Bug: gitlab pipeline considers manual trigger jobs as success before they are triggered
So, I have a gitlab-ci.yml that used to deploy to "staging", then "school", then have a manual deploy to "production", it worked as such:
To my suprise, this skipped manual deployment to school, but went on to deploy to production:
The documentation mentions:
on_success - execute job only when all jobs from prior stages succeed (or are considered succeeding because they are marked allow_failure). This is the default.
Note that hard-setting when: on_success
on the deploy prod job has no effect (i still had to manually cancel deploy to production before it started !)
Is it normal that a skipped job is considered successful by the next job stage ?
If so, how to workaround ? Will I need two manual deploys ? Or will I have to group "school" and "production" in the same stage (I would prefer to keep "school" before "production" just in case).
Thanks