-
Notifications
You must be signed in to change notification settings - Fork 4
/
azure-pipelines.yml
53 lines (44 loc) · 1.35 KB
/
azure-pipelines.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
# Node.js
# Build a general Node.js project with npm. test Auto trigger CI checking again again again Testing with new pip-line
# Add steps that analyze code, save build artifacts, deploy, and more:
# https://docs.microsoft.com/azure/devops/pipelines/languages/javascript
# Testing
trigger:
- main
# no PR triggers
pr: none
pool:
vmImage: "ubuntu-latest"
steps:
- task: NodeTool@0
inputs:
versionSpec: "12.x"
displayName: "Install Node.js"
- task: Npm@1
inputs:
command: "install"
- script: npm run build
env:
COSMOS_DB_KEY: ${COSMOS_DB_KEY}
RECAPTCHA_SECRET: ${RECAPTCHA_SECRET}
STAFF_VIEW_ALLOWED_IPS: ${STAFF_VIEW_ALLOWED_IPS}
displayName: "npm build"
- task: ArchiveFiles@2
inputs:
rootFolderOrFile: "$(build.sourcesDirectory)"
includeRootFolder: false
- task: PublishBuildArtifacts@1
displayName: "Publish artifacts: drop"
- task: Veracode@3
inputs:
ConnectionDetailsSelection: "Endpoint"
AnalysisService: "Veracode Scan"
veracodeAppProfile: "$(system.teamProject)"
version: "$(build.buildNumber)"
filepath: "$(build.artifactstagingdirectory)"
createSandBox: false
createProfile: true
failTheBuildIfVeracodeScanDidNotInitiate: false
scanStatusCheckInterval: "60"
importResults: false
failBuildOnPolicyFail: false