[PATCH v2] ci: Switch to native trigger

[PATCH v2] ci: Switch to native trigger

[Jan Kiszka]

From: Jan Kiszka <jan.kiszka@siemens.com>

Now that we are running both pipelines on the same server, we can also
make use of native gitlab-ci trigger mechanism. This both obsoletes the
need to configure a token and avoids starting a real job on a real
runner, just for calling curl.

This also improves the visualization of the two related pipelines in the
gitlab UI.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---

Changes in v2:
 - keep triggering "next" pipeline of xenomai-image

 .gitlab-ci.yml | 13 ++++++-------
 1 file changed, 6 insertions(+), 7 deletions(-)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 4d207dbd61..a80b4dc277 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -257,11 +257,10 @@ i386-userland:
 
 trigger-xenomai-images:
   stage: test
-  image: curlimages/curl
-  script:
-    - curl -X POST -F "token=${XENOMAI_IMAGES_TOKEN}"
-           -F "ref=${XENOMAI_IMAGES_BRANCH}"
-           -F "variables[ONLY_RUN]=${CI_COMMIT_BRANCH}"
-           https://source.denx.de/api/v4/projects/479/trigger/pipeline
+  variables:
+    ONLY_RUN: ${CI_COMMIT_BRANCH}
+  trigger:
+    project: xenomai/xenomai-images
+    branch: next
   rules:
-    - if: '$XENOMAI_IMAGES_TOKEN != "" && ($CI_COMMIT_BRANCH == "next" || $CI_COMMIT_BRANCH =~ /stable\/.*/)'
+    - if: '$CI_COMMIT_BRANCH == "next" || $CI_COMMIT_BRANCH =~ /stable\/.*/'
-- 
2.35.3