Open Stack

On Thu, Aug 6, 2015 at 8:12 AM, Dan Prince <dprince at redhat.com> wrote:

>
> One more side effect is that I think it also means we no longer have
> the capability to test arbitrary Zuul refspecs for projects like Heat,
> Neutron, Nova, or Ironic in our undercloud CI jobs. We've relied on the
> source-repositories element to do this for us in the undercloud and
> since most of the instack stuff uses packages I think we would loose
> this capability.
>
> I'm all for testing with packages mind you... would just like to see us
> build packages for any projects that have Zuul refspecs inline, create
> a per job repo, and then use that to build out the resulting instack
> undercloud.
>
> This to me is the biggest loss in our initial switch to instack
> undercloud for CI. Perhaps there is a middle ground here where instack
> (which used to support tripleo-image-elements itself) could still
> support use of the source-repositories element in one CI job until we
> get our package building processes up to speed?

Isn't this what's happening at line 89 in
https://review.openstack.org/#/c/185151/6/toci_devtest_instack.sh ?

Or would $ZUUL_CHANGES not be populated when check-experimental is run?



-- 
-- James Slagle
--