-
-
Notifications
You must be signed in to change notification settings - Fork 197
212 lines (198 loc) · 6.79 KB
/
node.js.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
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
# This workflow will do a clean install of node dependencies, build the source code and run tests across different versions of node
# For more information see: https://help.github.com/actions/language-and-framework-guides/using-nodejs-with-github-actions
name: Node.js CI
on: [pull_request]
env:
TOKEN_FLOW_APP_URL: ${{ secrets.TOKEN_FLOW_APP_URL }}
jobs:
# install dependencies and store artifact
package:
name: Create Package
runs-on: ubuntu-22.04
steps:
# 1: Setup node
- name: Setup Node.js
uses: actions/setup-node@v3
with:
node-version: '16.x'
# 2: Checkout repository
- name: Checkout repository
uses: actions/checkout@v2
- name: Cache node modules
id: cache-nodemodules
uses: actions/cache@v3
env:
cache-name: cache-node-modules
with:
# caching node_modules
path: node_modules
key: ${{ runner.os }}-node-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
restore-keys: |
${{ runner.os }}-node-${{ env.cache-name }}-
# 3: Install dependencies
- name: Install dependencies
if: steps.cache-nodemodules.outputs.cache-hit != 'true'
run: npm ci
# 5: Build package
- name: Build Package
run: npm run build
# 6: Store artifact
- name: Store Artifact
uses: actions/upload-artifact@v2
with:
name: package
path: |
dist
manifest.json
# install dependencies and run test command
test:
name: Tests
runs-on: ubuntu-latest
steps:
# 1: Setup node
- name: Setup Node.js
uses: actions/setup-node@v1
with:
node-version: '16.x'
# 2: Checkout repository
- name: Checkout repository
uses: actions/checkout@v2
# 3: Install dependencies.
- name: Cache node modules
id: cache-nodemodules
uses: actions/cache@v3
env:
cache-name: cache-node-modules
with:
# caching node_modules
path: node_modules
key: ${{ runner.os }}-node-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
restore-keys: |
${{ runner.os }}-node-${{ env.cache-name }}-
# This is very unlikely to happen, but we include it anyway in case some cache flushing happens
- name: Install dependencies
if: steps.cache-nodemodules.outputs.cache-hit != 'true'
run: npm ci
# 4: Run tests
- name: Run test command
run: npm run test
coverage:
name: Test coverage
continue-on-error: true
runs-on: ubuntu-22.04
steps:
# 1: Setup node
- name: Setup Node.js
uses: actions/setup-node@v3
with:
node-version: '16.x'
# 2: Checkout repository
- name: Checkout repository
uses: actions/checkout@v2
# 3: Install dependencies.
- name: Cache node modules
id: cache-nodemodules
uses: actions/cache@v3
env:
cache-name: cache-node-modules
with:
# caching node_modules
path: node_modules
key: ${{ runner.os }}-node-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
restore-keys: |
${{ runner.os }}-node-${{ env.cache-name }}-
# This is very unlikely to happen, but we include it anyway in case some cache flushing happens
- name: Install dependencies
if: steps.cache-nodemodules.outputs.cache-hit != 'true'
run: npm ci
# 4: Run test coverage report
- name: Run test coverage report
id: testCoverage
uses: anuraag016/Jest-Coverage-Diff@master
with:
fullCoverageDiff: false
runCommand: 'LAUNCHDARKLY_FLAGS=tokenThemes,gitBranchSelector,multiFileSync,tokenFlowButton npx jest --collectCoverageFrom=''["src/**/*.{js,jsx,ts,tsx}"]'' --coverage --collectCoverage=true --coverageDirectory=''./'' --coverageReporters=''json-summary'' --forceExit --detectOpenHandles '
afterSwitchCommand: npm ci
useSameComment: true
test-transform:
name: Transformer Tests
runs-on: ubuntu-22.04
steps:
# 1: Setup node
- name: Setup Node.js
uses: actions/setup-node@v3
with:
node-version: '16.x'
# 2: Checkout repository
- name: Checkout repository
uses: actions/checkout@v2
# 3: Install dependencies.
- name: Cache node modules
id: cache-nodemodules
uses: actions/cache@v3
env:
cache-name: cache-node-modules
with:
# caching node_modules
path: node_modules
key: ${{ runner.os }}-node-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
restore-keys: |
${{ runner.os }}-node-${{ env.cache-name }}-
# This is very unlikely to happen, but we include it anyway in case some cache flushing happens
- name: Install dependencies
if: steps.cache-nodemodules.outputs.cache-hit != 'true'
run: npm ci
# 4: Build package
- name: build:transform
run: npm run build-transform
# 5: Install dependencies
- name: Install dependencies - transformer
run: cd token-transformer && npm ci
# 6: Run tests
- name: Run test command
run: cd token-transformer && npm run test
cypress-run:
name: Cypress
runs-on: ubuntu-22.04
steps:
# 1: Checkout repository
- name: Checkout
uses: actions/checkout@v2
# 2: Install NPM dependencies, cache them correctly
# and run all Cypress tests
- name: Cypress run
uses: cypress-io/github-action@v2
with:
build: npm run build:cy
start: npm run serve
performance:
name: Performance
runs-on: ubuntu-22.04
steps:
# 1: Setup node
- name: Setup Node.js
uses: actions/setup-node@v3
with:
node-version: '16.x'
# 2: Checkout repository
- name: Checkout repository
uses: actions/checkout@v2
# 3: Install dependencies.
- name: Cache node modules
id: cache-nodemodules
uses: actions/cache@v3
env:
cache-name: cache-node-modules
with:
# caching node_modules
path: node_modules
key: ${{ runner.os }}-node-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
restore-keys: |
${{ runner.os }}-node-${{ env.cache-name }}-
# This is very unlikely to happen, but we include it anyway in case some cache flushing happens
- name: Install dependencies
if: steps.cache-nodemodules.outputs.cache-hit != 'true'
run: npm ci
# 4: Build package
- name: Run benchmark
run: npm run benchmark:build && npm run benchmark:run