Open Stack

Antoine,

Yes, I ran into same confusion recently. For dependent pipeline, Zuul will provide the same ZUUL_REF for each repo that has pipeline changes to test. So in test of second change, if you check out the $ZUUL_REF version for both repos, you'll indeed get the change set you want:

>  repoA with change 1
>  repoB with change 2

-Steve

> -----Original Message-----
> From: Antoine Musso [mailto:hashar at free.fr]
> Sent: Friday, January 03, 2014 09:27
> To: OpenStack Infra
> Subject: [OpenStack-Infra] Zuul gating changes in different projects
> 
> Hello,
> 
> For Wikimedia, I am finally working on getting some gating jobs that are
> shared by multiple Gerrit projects.  I am not sure though how to get the
> patches applied properly, and would love some enlightenment.
> 
> If I get repoA and repoB tested with a dependentPipeline, doing
> respectively a change 1 and change 2 and approving them in sequence, the
> queue would be:
> 
>  - repoA, change 1
>  - repoB, change 2
> 
> The jobs triggered for the first entry should thus be testing:
> 
>  repoA with change 1
>  repoB using master branch
> 
> For the second entry:
> 
>  repoA with change 1
>  repoB with change 2
> 
> 
> I have looked at the openstack-infra/devstack-gate script named
> devstack-vm-gate-wrap.sh but it seems to only apply the triggered change
> and let over repositories use the master branch. So the layout for the
> second entry would be:
> 
>  repoA with master   (instead of change 1)
>  repoB with change 2
> 
> I am fairly sure I am missing something :-(  Any pointer welcome!
> 
> cheers,
> 
> --
> Antoine "hashar" Musso
> 
> _______________________________________________
> OpenStack-Infra mailing list
> OpenStack-Infra at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra