-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
build: adapted name of maven repo to Azure DevOps Environment for partners ci: updated pipeline-stub to get template from public git repo
- Loading branch information
Showing
2 changed files
with
58 additions
and
19 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,25 +1,64 @@ | ||
# see https://docs.microsoft.com/en-us/azure/devops/pipelines/process/resources?view=azure-devops&tabs=schema#define-a-repositories-resource | ||
# 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: IOMDevopsRepo | ||
type: git | ||
name: order-iom-partner-devops | ||
ref: develop | ||
- 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: | ||
- '*' | ||
|
||
# see https://docs.microsoft.com/en-us/azure/devops/pipelines/process/templates?view=azure-devops#extend-from-a-template | ||
# see https://docs.microsoft.com/en-us/azure/devops/pipelines/process/templates?view=azure-devops#use-other-repositories | ||
extends: | ||
template: template.yml@IOMDevopsRepo | ||
parameters: | ||
agentPool: ubuntu-20.4-DS4_v2-adopt-adoptium-jdk-ora | ||
artifactsFeed: order-iom-releases | ||
dockerRepoIOMServiceConnection: order-iom-docker.tools.intershop.com | ||
dockerRepoIOM: docker.tools.intershop.com/iom/intershophub | ||
acrServiceConnection: order-iomInternalACR-ISH-ENG-IOM | ||
acr: iominternalacr.azurecr.io | ||
projectEnvName: dev | ||
# 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)" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters