-
Notifications
You must be signed in to change notification settings - Fork 0
/
azure-pipelines.yml
64 lines (58 loc) · 2.99 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
57
58
59
60
61
62
63
64
# Library iom-build-configuration is provided by Intershops DevOps Environment. It provides
# the following variables:
# - BUILD_AGENT_POOL: name of the build agent pool
# - REPO_SERVICE_CONNECTION: service connection to the customer ACR
# - REPO_PATH: host name and path of the customer ACR
# - INTERSHOP_REPO_SERVICE_CONNECTION: service connection to the Intershop container registry
# - INTERSHOP_REPO_PATH: host name and path of the Intershop container registry
variables:
- group: iom-build-configuration
# Create a repository resource to the Github repo, that is providing the centrally managed CI job.
resources:
repositories:
- repository: iom-partner-devops
type: github
endpoint: INTERSHOP_GITHUB
name: intershop/iom-partner-devops
ref: main
# Define, when the pipeline should be triggered.
# See https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/azure-repos-git?view=azure-devops&tabs=yaml#ci-triggers
trigger:
branches:
include:
- '*'
# Run CI job. Additional custom stages/jobs might be added, see example below.
stages:
- stage: CI
jobs:
- template: ci-job-template.yml@iom-partner-devops
parameters:
# You have to set here the name of the environment, that is providing the CI specific configuration!
projectEnvName: dev
# Project images, built and tested by the DevOps pipeline, are published to the project ACR only, if
# the name of the branch matches the regex passed in parameter branchesForPublication. If the default
# behavior does not fit your requirements, activate the following line and adapt the regular expression.
#branchesForPublication: '^refs/heads/develop$\|^refs/heads/master$\|^refs/heads/main$\|^refs/heads/release/\|^refs/heads/hotfix/'
# These parameters must not be changed. They are used to pass variables to the ci-job templaten, which
# are defined by library iom-build-configuration.
agentPool: $(BUILD_AGENT_POOL)
artifactsFeed: iom-maven-artifacts
dockerRepoIOMServiceConnection: $(INTERSHOP_REPO_SERVICE_CONNECTION)
dockerRepoIOM: $(INTERSHOP_REPO_PATH)
acrServiceConnection: $(REPO_SERVICE_CONNECTION)
acr: $(REPO_PATH)
# The following block shows a very simple example, how to extend the DevOps pipeline by a custom
# job. Alternatively one or more stages could be added, see:
# https://docs.microsoft.com/en-us/azure/devops/pipelines/process/stages?view=azure-devops
#- job: custom
# pool: $(BUILD_AGENT_POOL)
# continueOnError: false
# timeoutInMinutes: 5
# workspace:
# clean: all
# steps:
# - checkout: self
# path: project
# clean: true
# timeoutInMinutes: 5
# displayName: "Checkout IOM project @$(Build.SourceBranchName)"