-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathazure-pipelines-simplificado.yml
51 lines (46 loc) · 1.58 KB
/
azure-pipelines-simplificado.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
# Node
trigger:
- master
pool:
vmImage: ubuntu-latest
variables:
- group: Veracode
steps:
# Fazemos o empacotamento dos arquivos conforme o guia da Veracode:
# https://docs.veracode.com/r/c_comp_quickref
- task: ArchiveFiles@2
inputs:
rootFolderOrFile: '$(Agent.BuildDirectory)'
includeRootFolder: true
archiveType: 'zip'
archiveFile: '$(caminhoPacote)'
replaceExistingArchive: true
displayName: 'Criando pacote para analise'
# Utilizamos a task da Veracode para iniciar um scan unificado de SCA e SAST
# Fazemos a autenticação com a Service Connection chamada "veracode-evento"
# Enviamos para a analise o ZIP que geramos na etapa anterior
- task: Veracode@3
inputs:
ConnectionDetailsSelection: 'Endpoint'
AnalysisService: 'veracode-evento'
veracodeAppProfile: '$(veracodeAppProfile)'
version: '$(build.buildNumber)'
filepath: '$(caminhoPacote)'
createProfile: true
importResults: true
maximumWaitTime: '360'
displayName: 'Veracode SAST'
# Após o termino da analise, recebemos os resultados e transformamos qualquer falha encontrar em um novo card no Boards
- task: Veracode Flaw Importer@3
inputs:
ConnectionDetailsSelection: 'Endpoint'
AnalysisService: 'veracode-evento'
veracodeAppProfile: '$(veracodeAppProfile)'
sandboxName:
scanType: 'Dynamic, Static, and Software Composition Analysis'
importType: 'All Unmitigated Flaws Violating Policy'
workItemType: 'Issue'
area: '$(system.teamProject)'
overwriteAreaPathInWorkItemsOnImport: true
flawImportLimit: '1000'
displayName: 'Veracode importando falhas'