Skip to content

Add workflow rules to avoid MR pipelines

Marcel Amirault requested to merge update-pipeline-config-skip-mr-pipelines into master

What does this MR do?

As reported in !2719 (comment 1057289939) and then gitlab-org/gitlab!94429 (comment 1057772648), an update to the latest SAST templates can now trigger pipelines. We should add a workflow: rules section to blow those pipelines, as they are not in use in this project. All other pipelines as still allowed, thanks to the final when: always.,

Related issues

Resolves #3469 (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

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 omnibus-gitlab opened
Edited by Jason Plum

Merge request reports