forked from Ba4bes/Bicep-NamingConvention
-
Notifications
You must be signed in to change notification settings - Fork 0
/
azure-pipelines.yml
56 lines (51 loc) · 1.57 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
54
55
56
# Starter pipeline
# Start with a minimal pipeline that you can customize to build and deploy your code.
# Add steps that build, run tests, deploy, and more:
# https://aka.ms/yaml
trigger:
- none
pool:
vmImage: ubuntu-latest
steps:
- task: AzureCLI@2
displayName: 'build bicep artifact'
inputs:
azureSubscription: 'AzureConnection'
scriptType: 'pscore'
scriptLocation: 'inlineScript'
inlineScript: |
az bicep build --file main.bicep --outfile ./main.json
- task: PowerShell@2
inputs:
targetType: 'inline'
script: |
$Data = @{
TemplatePath = './main.json'
MandatoryTags = @(
'Owner'
'CostCenter'
'Environment'
'DeploymentDate'
)
TagParameterName = 'tags'
TagModuleName = 'tagging'
}
$container = New-PesterContainer -Path '.\tests\tags.tests.ps1' -Data $Data
$outputFile = ".\TEST-RESULTS.xml"
$config = New-PesterConfiguration
$config.TestResult.Enabled = $true
$config.TestResult.OutputFormat = "NUnitXML"
$config.TestResult.OutputPath = $outputFile
$config.Output.Verbosity = "Detailed"
$config.Run.PassThru = $true
$config.Run.Container = $container
Invoke-Pester -Configuration $config
- task: PublishTestResults@2
displayName: Publish Test Results
condition: always()
inputs:
testRunTitle: 'Test Results for Pester'
buildPlatform: 'Windows'
testRunner: 'NUnit'
testResultsFiles: "TEST-RESULTS.xml"
failTaskOnFailedTests: true