Skip to content
Snippets Groups Projects
Commit 38379173 authored by Tim Jaacks's avatar Tim Jaacks
Browse files

Run yamllint job on gitlab-ci integrations

Otherwise no pipeline is created at all in these merge requests, which
prevents the MR from being merged.
parent dce4f8a3
No related branches found
No related tags found
1 merge request!194Run yamllint job on gitlab-ci integrations
Pipeline #28355 waiting for manual action with stages
in 1 minute and 45 seconds
...@@ -37,9 +37,6 @@ workflow: ...@@ -37,9 +37,6 @@ workflow:
when: never when: never
- if: $CI_MERGE_REQUEST_SOURCE_PROJECT_ID != $CI_MERGE_REQUEST_PROJECT_ID - if: $CI_MERGE_REQUEST_SOURCE_PROJECT_ID != $CI_MERGE_REQUEST_PROJECT_ID
when: never when: never
# Do not run pipeline for integrate/gitlab-ci/ integrations
- if: $CI_COMMIT_REF_NAME =~ /^integrate\/gitlab-ci\/.*/
when: never
# FIXME: Unfortunately we cannot use variables in regular expressions due to a # FIXME: Unfortunately we cannot use variables in regular expressions due to a
# GitLab limitation: https://gitlab.com/gitlab-org/gitlab/-/issues/209904 # GitLab limitation: https://gitlab.com/gitlab-org/gitlab/-/issues/209904
# As soon as this get fixed, use the regex based rules below instead of checking # As soon as this get fixed, use the regex based rules below instead of checking
...@@ -57,9 +54,14 @@ workflow: ...@@ -57,9 +54,14 @@ workflow:
# -------------------------------------------------------------------------------------- # --------------------------------------------------------------------------------------
# Stage: infrastructure # Stage: infrastructure
# -------------------------------------------------------------------------------------- # --------------------------------------------------------------------------------------
.skip-for-gitlab-ci-integrations:
rules:
- if: $CI_COMMIT_REF_NAME !~ /^integrate\/gitlab-ci\/.*/
generate-pipelines: generate-pipelines:
extends: extends:
- .infrastructure - .infrastructure
- .skip-for-gitlab-ci-integrations
script: script:
# The job generation script implicitly passes the OS environment to the template, so # The job generation script implicitly passes the OS environment to the template, so
# that the template has access to all GitLab CI variables. Hence there is no need # that the template has access to all GitLab CI variables. Hence there is no need
...@@ -73,6 +75,8 @@ generate-pipelines: ...@@ -73,6 +75,8 @@ generate-pipelines:
- manifest-integration-pipelines.yml - manifest-integration-pipelines.yml
trigger-pipelines: trigger-pipelines:
extends:
- .skip-for-gitlab-ci-integrations
stage: infrastructure stage: infrastructure
needs: needs:
- generate-pipelines - generate-pipelines
......
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