Le 17/06/2015 19:49, S Page a écrit :
#1 sounds right, Jenkins serves us, not vice versa. The core change's commit message should reference the two required extension changes.
Whenever we upgrade Zuul, it will recognize in the commit summary messages headers like "Depends-On: <gerrit-change-id>"
So the mediawiki/core change can have something like:
Break API foo
Depends-On: I1AE2309409 # fix for Flow
When you propose the patch to core, it will be tested with the dependent change that is still open in Gerrit (ie it has not been merged yet).
Then you would +2 the changes. Zuul will first test the extension change as if the core patch has been merged. If it passes it get merged if it fails, the core change behind is rejected automatically.
That is nicknamed cross-repo dependency: http://lists.openstack.org/pipermail/openstack-dev/2015-February/056515.html
No plan to upgrade our Zuul in the short term though ;(