Skip to content

Enable reporting pipelines triggered from ops

George Koltsov requested to merge ml-report-pipelines-triggered-from-ops into master

This includes staging-orchestrated pipelines, which should be reported but currently aren't.

A deployer job triggers a pipeline in this project, e.g.: https://ops.gitlab.net/gitlab-com/gl-infra/deployer/-/jobs/1785880

$ bundle exec deploy-tooling/pipeline-trigger/bin/pipeline-trigger $TRIGGER_ARGS
2020-09-07 12:34:09.032542 I Trigger::Qa -- Triggered downstream pipeline -- {:web_url=>"https://ops.gitlab.net/gitlab-org/gitlab-qa/-/pipelines/255077", :id=>255077, :project=>"gitlab-org/gitlab-qa", :variables=>["NOTIFY_CHANNEL=qa-staging", "TOP_UPSTREAM_SOURCE_JOB=https://ops.gitlab.net/gitlab-com/gl-infra/deployer/-/jobs/1785880", "RELEASE=dev.gitlab.org:5005/gitlab/omnibus-gitlab/gitlab-ee:13.4.202009071120-1fdd4a7ab43.e571559f17c"]}

So we can pattern match TOP_UPSTREAM_SOURCE_JOB to detect if any pipeline on ops.gitlab.net triggers a pipeline here.

Edited by George Koltsov

Merge request reports

Loading