Skip to content
Snippets Groups Projects
Verified Commit 1366a3ae authored by Alex Pott's avatar Alex Pott
Browse files

Issue #3420042 by fjgarlin, longwave, catch: Bring external template files into core

parent a6ba33b2
No related branches found
No related tags found
No related merge requests found
# cspell:ignore codequality Micheh micheh # cspell:ignore codequality Micheh micheh webide
################ ################
# Drupal GitLabCI template. # Drupal GitLabCI template.
...@@ -12,23 +12,35 @@ ...@@ -12,23 +12,35 @@
################ ################
################ ################
# Includes # Workflow
# #
# Additional configuration can be provided through includes. # Define conditions for when the pipeline will run.
# One advantage of include files is that if they are updated upstream, the # For example:
# changes affect all pipelines using that include. # * On commit
# * On merge request
# * On manual trigger
# * etc.
# https://docs.gitlab.com/ee/ci/jobs/job_control.html#specify-when-jobs-run-with-rules
# #
# Includes can be overridden by re-declaring anything provided in an include, # Pipelines can also be configured to run on a schedule,though they still must meet the conditions defined in Workflow and Rules. This can be used, for example, to do nightly regression testing:
# here in gitlab-ci.yml. # https://gitlab.com/help/ci/pipelines/schedules
# https://docs.gitlab.com/ee/ci/yaml/includes.html#override-included-configuration-values
################ ################
include: workflow:
- project: $_GITLAB_TEMPLATES_REPO rules:
ref: $_GITLAB_TEMPLATES_REF # These 3 rules from https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/ci/templates/Workflows/MergeRequest-Pipelines.gitlab-ci.yml
file: # Run on merge requests
- '/includes/include.drupalci.variables.yml' - if: $CI_PIPELINE_SOURCE == 'merge_request_event'
- '/includes/include.drupalci.workflows.yml' # Run when called from an upstream pipeline https://docs.gitlab.com/ee/ci/pipelines/downstream_pipelines.html?tab=Multi-project+pipeline#use-rules-to-control-downstream-pipeline-jobs
- if: $CI_PIPELINE_SOURCE == 'pipeline'
# Run on commits.
- if: $CI_PIPELINE_SOURCE == "push" && $CI_PROJECT_ROOT_NAMESPACE == "project"
# The last rule above blocks manual and scheduled pipelines on non-default branch. The rule below allows them:
- if: $CI_PIPELINE_SOURCE == "schedule" && $CI_PROJECT_ROOT_NAMESPACE == "project"
# Run if triggered from Web using 'Run Pipelines'
- if: $CI_PIPELINE_SOURCE == "web"
# Run if triggered from WebIDE
- if: $CI_PIPELINE_SOURCE == "webide"
################ ################
# Variables # Variables
...@@ -42,7 +54,7 @@ include: ...@@ -42,7 +54,7 @@ include:
################ ################
variables: variables:
COMPOSER: composer.json _CONFIG_DOCKERHUB_ROOT: "drupalci"
# Let composer know what self.version means. # Let composer know what self.version means.
COMPOSER_ROOT_VERSION: "${CI_MERGE_REQUEST_TARGET_BRANCH_NAME}${CI_COMMIT_BRANCH}-dev" COMPOSER_ROOT_VERSION: "${CI_MERGE_REQUEST_TARGET_BRANCH_NAME}${CI_COMMIT_BRANCH}-dev"
CONCURRENCY: 24 CONCURRENCY: 24
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment