forked from dotnet/vscode-dotnet-runtime
-
Notifications
You must be signed in to change notification settings - Fork 0
/
1pr-azure-pipeline.yml
67 lines (63 loc) · 1.84 KB
/
1pr-azure-pipeline.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
# Name: dotnet.vscode-dotnet-runtime
# URL: https://dev.azure.com/dnceng-public/public/_build?definitionId=60
trigger:
batch: true
branches:
include:
- main
tags:
include:
- SDK-v*
- Runtime-v*
pr:
autoCancel: false
branches:
include:
- '*'
variables:
- name: Codeql.Enabled
value: true
# The public PR pool schema is different from the 1ES one. We use 'vmImage' which is a default azure pipeline schema. 'os' and 'name' have nothing to do with image selection here.
# 1ES uses 'image' but defining an image this way using our public pools duseOneEngineeringPool not work as they aren't configured this way.
# We can later add the flag 'useOneEngineeringPool' or one engineering system: false or true in all tasks to determine if we use vmImage or a 1es pool object.
parameters:
- name: pools
type: object
default:
- name: NetCore-Public
vmImage: ubuntu-latest
os: linux
- name: NetCore-Public
vmImage: macOS-latest
os: macOS
- name: NetCore-Public
vmImage: windows-latest
os: windows
stages:
- stage: o # o is just used so it looks like a bullet point in the output of devops
jobs:
- ${{ each image in parameters.pools }}:
- template: pipeline-templates/build-test.yaml
parameters:
pool:
vmImage: ${{ image.vmImage }}
os: ${{ image.os }}
useOneEngineeringPool: false
- template: pipeline-templates/upstream-verify.yaml
parameters:
pool:
vmImage: windows-latest
os: windows
useOneEngineeringPool: false
- template: pipeline-templates/lint.yaml
parameters:
pool:
vmImage: windows-latest
os: windows
useOneEngineeringPool: false
- template: pipeline-templates/package-vsix.yaml
parameters:
pool:
vmImage: windows-latest
os: windows
useOneEngineeringPool: false