Gemnasium executes child pipelines when job of first stage fail
Summary
Merge request pipelines of Gemnasium move on to the child pipelines (for the three analyzers) even when jobs of first stage fail, and they're not allowed to fail. See https://gitlab.com/gitlab-org/security-products/analyzers/gemnasium/-/pipelines/598217255
This might impact branch pipelines as well. To be checked.
This impacts developers but does NOT impact users.
Steps to reproduce
Create a MR pipeline where the go linter fails.
What is the current bug behavior?
Child pipelines are executed.
What is the expected correct behavior?
Child pipelines should NOT be executed.
Relevant logs and/or screenshots
Possible fixes
Change the when
param from always
to on_success
, in the rules of the trigger
. See gitlab-org/security-products/analyzers/gemnasium!363 (comment 1056788170)
/cc @adamcohen @brytannia
Edited by Fabien Catteau