WIP: Demonstrate that repo configured with gitlab-ci.yml can run salsa-ci.yml

Author: ottok

debian/gitlab-ci.yml

@@ -1,43 +1,7 @@
-# DO NOT MODIFY
-# This file was automatically generated from authoritative copy at:
-# https://salsa.debian.org/go-team/infra/pkg-go-tools/blob/master/config/gitlabciyml.go
 ---
-stages:
-  - test
-  - package
-
+# This 'gitlab-ci.yml' file exists for the sole purpose of loading
+# 'salsa-ci.yml' in case the GitLab repository is still configured to use old
+# name 'gitlab-ci.yml'. Please migrate to use 'salsa-ci.yml' and delete this
+# file.
 include:
-  - project: go-team/infra/pkg-go-tools
-    ref: master
-    file: pipeline/test-archive.yml
-    # Run the Go team CI only in the go-team project that has access to GitLab
-    # CI runners tagged 'go-ci'
-    rules:
-      - if: $CI_PROJECT_ROOT_NAMESPACE  == "go-team"
-
-# Additionally run Salsa CI only if the Play button is pressed on the pipeline
-Salsa CI:
-  stage: package
-  trigger:
-    include:
-      - project: salsa-ci-team/pipeline
-        ref: master
-        file: recipes/debian.yml
-    strategy: depend
-  rules:
-    - if: $CI_PIPELINE_SOURCE == "push" # Only trigger pipelines on pushes
-      when: manual
-    - if: $CI_PIPELINE_SOURCE == "merge_request_event" # Or on merge requests
-      when: always
-  variables:
-    SALSA_CI_DISABLE_REPROTEST: 1 # Disable to save CI runner resources
-
-# If Salsa CI is not running at
-# https://salsa.debian.org/%{project_path}/-/pipelines, ensure that
-# https://salsa.debian.org/%{project_path}/-/settings/ci_cd has in field "CI/CD
-# configuration file" the same filename as this file.
-#
-# If Salsa CI is running, but first job is stuck because the project doesn't
-# have any runners online assigned to it, ensure that
-# https://salsa.debian.org/%{project_path}/-/settings/ci_cd has under "Runners"
-# the setting for "Enable instance runners for this project" enabled.
+  - local: 'debian/salsa-ci.yml'

debian/salsa-ci.yml

@@ -0,0 +1,43 @@
+# DO NOT MODIFY
+# This file was automatically generated from authoritative copy at:
+# https://salsa.debian.org/go-team/infra/pkg-go-tools/blob/master/config/gitlabciyml.go
+---
+stages:
+  - test
+  - package
+
+include:
+  - project: go-team/infra/pkg-go-tools
+    ref: master
+    file: pipeline/test-archive.yml
+    # Run the Go team CI only in the go-team project that has access to GitLab
+    # CI runners tagged 'go-ci'
+    rules:
+      - if: $CI_PROJECT_ROOT_NAMESPACE  == "go-team"
+
+# Additionally run Salsa CI only if the Play button is pressed on the pipeline
+Salsa CI:
+  stage: package
+  trigger:
+    include:
+      - project: salsa-ci-team/pipeline
+        ref: master
+        file: recipes/debian.yml
+    strategy: depend
+  rules:
+    - if: $CI_PIPELINE_SOURCE == "push" # Only trigger pipelines on pushes
+      when: manual
+    - if: $CI_PIPELINE_SOURCE == "merge_request_event" # Or on merge requests
+      when: always
+  variables:
+    SALSA_CI_DISABLE_REPROTEST: 1 # Disable to save CI runner resources
+
+# If Salsa CI is not running at
+# https://salsa.debian.org/%{project_path}/-/pipelines, ensure that
+# https://salsa.debian.org/%{project_path}/-/settings/ci_cd has in field "CI/CD
+# configuration file" the same filename as this file.
+#
+# If Salsa CI is running, but first job is stuck because the project doesn't
+# have any runners online assigned to it, ensure that
+# https://salsa.debian.org/%{project_path}/-/settings/ci_cd has under "Runners"
+# the setting for "Enable instance runners for this project" enabled.