-
Notifications
You must be signed in to change notification settings - Fork 13
/
appveyor.yml
72 lines (66 loc) · 2.77 KB
/
appveyor.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
version: 0.14.7.{build}
shallow_clone: true
# Don't actually build. This is not a .net project
build: off
# Cache yarn packages to speed up builds
cache:
#- "%LOCALAPPDATA%\\Yarn"
# restore NuGet packages before running MSBuild
before_build:
- echo APPVEYOR_PROJECT_NAME %APPVEYOR_PROJECT_NAME%
- echo APPVEYOR_PROJECT_SLUG %APPVEYOR_PROJECT_SLUG%
- echo APPVEYOR_BUILD_FOLDER %APPVEYOR_BUILD_FOLDER%
- echo APPVEYOR_BUILD_ID %APPVEYOR_BUILD_ID%
- echo APPVEYOR_BUILD_NUMBER %APPVEYOR_BUILD_NUMBER%
- echo APPVEYOR_BUILD_VERSION %APPVEYOR_BUILD_VERSION%
- echo APPVEYOR_REPO_NAME %APPVEYOR_REPO_NAME%
- echo APPVEYOR_REPO_BRANCH %APPVEYOR_REPO_BRANCH%
- echo APPVEYOR_REPO_TAG %APPVEYOR_REPO_TAG%
- echo APPVEYOR_REPO_TAG_NAME %APPVEYOR_REPO_TAG_NAME%
- echo APPVEYOR_REPO_COMMIT %APPVEYOR_REPO_COMMIT%
- echo APPVEYOR_REPO_COMMIT_TIMESTAMP %APPVEYOR_REPO_COMMIT_TIMESTAMP%
environment:
nodejs_version: "14"
install:
# Get the latest stable version of Node.js or io.js
- ps: Install-Product node $env:nodejs_version
- npm install -g yarn
# A pre-existing yarn.lock appears to confuse yarn with regards to @types packages, namely a * version
# does not go for the latest available version of said package when doing a "yarn install" with the
# new package version with a pre-existing yarn.lock. This causes a whole load of bogus duplicate identifer
# errors as dependent @types packages will now pull down a private copy of this * version dependency (that is
# not the latest one)
#
# Nuking the yarn.lock file before installing with the latest version of said package does not have this problem
# as the generated yarn.lock file will correctly show a * version package as the latest version
#
# UPDATE 01 Mar 2017: Unconditionally nuking yarn.lock does not play nice with in-range updates done by greenkeeper
# so I'll fall back to putting @types/react to the greenkeeper ignore list and manually updating this one package
# - del yarn.lock
# install packages, this will also do a production build as a postinstall
- yarn install
- yarn audit --groups "dependencies"
test_script:
- yarn --version
- yarn run ci:appveyor
artifacts:
- path: .\viewer.zip
name: viewer
type: zip
- path: .\storybook.zip
name: storybook
type: zip
- path: .\apidocs.zip
name: api_docs
type: zip
deploy:
release: $(appveyor_repo_tag_name)
description: 'Release $(appveyor_repo_tag_name) ($(appveyor_build_version))'
provider: GitHub
auth_token:
secure: Dw0UkS+M9jDa7xofORbKLKgTBWZsBTN56QA7xD7F0pCCdNqnLH3K5oFk3smWjRfX
artifact: /.*\.zip/
draft: true
prerelease: true
on:
APPVEYOR_REPO_TAG: true # deploy on tag push only