{"id":3692,"date":"2020-05-25T07:00:29","date_gmt":"2020-05-25T06:00:29","guid":{"rendered":"https:\/\/www.diogonunes.com\/blog\/?p=3692"},"modified":"2020-06-01T10:47:53","modified_gmt":"2020-06-01T09:47:53","slug":"gitlab-pipeline-triggering-pipeline-sync","status":"publish","type":"post","link":"https:\/\/www.diogonunes.com\/blog\/gitlab-pipeline-triggering-pipeline-sync\/","title":{"rendered":"Pipeline triggering pipeline on GitLab"},"content":{"rendered":"

\"\"<\/a><\/p>\n

Usually when configuring a GitLab pipeline (.gitlab-ci.yml<\/code>) you only care about steps in your own pipeline. Sometimes however, you may want to trigger other pipelines (of other repositories) as a step of your own pipeline.<\/p>\n

<\/p>\n

\n

Context: You have your app divided into multiple microservices\/repos. There’s another repo which contains a suite of End-to-End tests. That repo has a pipeline that, when triggered, runs the whole tests using the latest version of each app.<\/p>\n

Problem: At the end of your microservice’s pipeline, you deploy your latest version, and then you want to run the E2E pipeline, to make sure you didn’t break any previously working functionality. But that’s another repo…<\/p>\n<\/blockquote>\n

So the question is: how can you have a pipeline triggering another pipeline and wait<\/em> for the result?<\/strong><\/p>\n

Officially, you can’t<\/del> At the time, we were not able to use the official way<\/a>. Luckily for us, Sven A. Schmidt created a workaround<\/a>. The example below was adapted from his solution:<\/p>\n

variables:\n  GITLAB_API_PATH: \/api\/v4\/projects\n  GITLAB_HOST: TBD            # domain where your gitlab is hosted\n  PIPELINE_TRIGGER_IMAGE: registry.gitlab.com\/finestructure\/pipeline-trigger \n  # Secrets\n  PIPELINE_SERVICE_TOKEN: TBD # token of user that can invoke pipelines\n  PIPELINE_TRIGGER_TOKEN: TBD # token of the invoked repo, here's how http:\/\/tiny.cc\/2unvbz\n\ntrigger-pipeline:\n  image: $PIPELINE_TRIGGER_IMAGE\n  variables:\n    GIT_STRATEGY: none\n    TRIGGER_TARGET_REPO_ID: TBD # the GitLab ID of the repo you want to call\n  script:\n    - trigger --verbose -h $GITLAB_HOST -u $GITLAB_API_PATH\n      -a $TRIGGER_SOURCE_USER_TOKEN -p $TRIGGER_TARGET_REPO_TOKEN\n      -t master $TRIGGER_TARGET_REPO_ID\n      -e SOME_ENV_VAR=\"value goes here\" -e ANOTHER_ENV_VAR=$CAN_ALSO_READ_FROM_VARS\n<\/code><\/pre>\n
If you use this code you will create a job named trigger-pipeline<\/code> in your pipeline A, that when executed will call a pipeline B (TRIGGER_TARGET_REPO_ID<\/code>), and wait for that pipeline to finish.<\/p>\n