Skip to content

Use PIPELINE_TYPE logic for trigger jobs

Robert Marshall requested to merge pipeline-types-on-trigger-jobs-take-2 into master

What does this MR do?

Use PIPELINE_TYPE logic for trigger jobs

We could not originally use `PIPELINE_TYPE` for triggered jobs because
`inherit:variables` was set to false. If enabled, then passing the
`PIPELINE_TYPE` variable to the downstream pipeline would interfere with
the workflow rules calculation downstream.

Here, the passed variables are specified with each `if` clause to avoid
interference with the workflow rules calculation.

Closes https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/7225

Closes https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/7315

Signed-off-by: Balasankar "Balu" C <balasankar@gitlab.com>

Related issues

Closes #7225 (closed)

Closes #7315 (closed)

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion

Required

  • Merge Request Title, and Description are up to date, accurate, and descriptive
  • MR targeting the appropriate branch
  • MR has a green pipeline on GitLab.com
  • Pipeline is green on dev.gitlab.org if the change is touching anything besides documentation or internal cookbooks
  • trigger-package has a green pipeline running against latest commit

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes
  • Documentation created/updated
  • Tests added
  • Integration tests added to GitLab QA
  • Equivalent MR/issue for the GitLab Chart opened

Merge request reports