Different merge-mode for different pipeline?
Hello,
Is it possible to specify different merge-modes for different pipelines for the same repository? For example, is something like this possible in a zuul.yaml configuration:
- job: name: test run: playbooks/test.yaml - project: merge-mode: cherry-pick check: jobs: - test - project: merge-mode: merge-resolve gate: jobs: - test
The check pipeline would use cherry-pick as a merge mode, while the gate pipeline would use merge-resolve?
Thanks, Nick
Nick Hwangbo Nick.Hwangbo@wdc.com writes:
Hello,
Is it possible to specify different merge-modes for different pipelines for the same repository? For example, is something like this possible in a zuul.yaml configuration:
- job: name: test run: playbooks/test.yaml
- project: merge-mode: cherry-pick check: jobs: - test
- project: merge-mode: merge-resolve gate: jobs: - test
The check pipeline would use cherry-pick as a merge mode, while the gate pipeline would use merge-resolve?
No, it's a characteristic of the project because in both cases the idea is to determine whether a change will be able to merge. So we go out of our way to have Zuul simulate the final conditions as realistically as possible. So the check pipeline is really predicting what the gate pipeline will do, and the gate pipeline is predicting what the final state will be after merge.
-Jim
Hi Jim,
Thanks for the response and the explanation. We'll have to figure out another solution then, or redesign how we use the pipelines.
Thanks, Nick
-----Original Message----- From: James E. Blair corvus@inaugust.com Sent: Tuesday, May 28, 2019 1:27 PM To: zuul-discuss@lists.zuul-ci.org Subject: Re: Different merge-mode for different pipeline?
Nick Hwangbo Nick.Hwangbo@wdc.com writes:
Hello,
Is it possible to specify different merge-modes for different pipelines for the same repository? For example, is something like this possible in a zuul.yaml configuration:
- job: name: test run: playbooks/test.yaml
- project: merge-mode: cherry-pick check: jobs: - test
- project: merge-mode: merge-resolve gate: jobs: - test
The check pipeline would use cherry-pick as a merge mode, while the gate pipeline would use merge-resolve?
No, it's a characteristic of the project because in both cases the idea is to determine whether a change will be able to merge. So we go out of our way to have Zuul simulate the final conditions as realistically as possible. So the check pipeline is really predicting what the gate pipeline will do, and the gate pipeline is predicting what the final state will be after merge.
-Jim
_______________________________________________ Zuul-discuss mailing list Zuul-discuss@lists.zuul-ci.org http://lists.zuul-ci.org/cgi-bin/mailman/listinfo/zuul-discuss
participants (2)
-
corvus@inaugust.com
-
Nick Hwangbo