WIP: Use latest gitlab-ci.yml with Salsa CI support

Sync latest version from https://salsa.debian.org/go-team/infra/pkg-go-tools/blob/master/config/gitlabciyml.go

Author: ottok

debian/gitlab-ci.yml

@@ -1,6 +1,43 @@
-# auto-generated, DO NOT MODIFY.
-# The authoritative copy of this file lives at:
+# 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:
-  - https://salsa.debian.org/go-team/infra/pkg-go-tools/-/raw/master/pipeline/test-archive.yml
+  - 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.