[all] Long overdue cleanups of Zuulv2 compatibility base configs
fungi at yuggoth.org
Mon Jun 24 17:20:43 UTC 2019
On 2019-06-20 19:58:49 +0000 (+0000), Jeremy Stanley wrote:
> On 2019-06-04 22:45:58 +0000 (+0000), Clark Boylan wrote:
> > As part of our transition to Zuulv3 a year and a half ago, we
> > carried over some compatibility tooling that we would now like
> > to clean up. Specifically, we add a zuul-cloner (which went away
> > in zuulv3) shim and set a global bindep fallback file value in
> > all jobs. Zuulv3 native jobs are expected to use the repos zuul
> > has precloned for you (no zuul-cloner required) as well as
> > supply an in repo bindep.txt (or specify a bindep.txt path or
> > install packages via some other method).
> > This means that we should be able to remove both of these items
> > from the non legacy base job in OpenDev's zuul. The legacy base
> > job will continue to carry these for you so that you can write
> > new native jobs over time. We have two changes  ready to
> > go for this
> > Our current plan is to merge these changes on June 24, 2019. We
> > will be around to help debug any unexpected issues that come up.
> > Jobs can be updated to use the "legacy-base" base job instead of
> > the "base" base job if they need to be reverted to the old
> > behavior quickly.
> >  https://review.opendev.org/656195
> >  https://review.opendev.org/663151
> Obvious uncaught breakage to look out for on Monday will be
> failures revolving around "command not found" errors for
> zuul-cloner or other commands which may have been provided by one
> of the packages in the
> <URL: https://opendev.org/openstack/project-config/src/commit/e2100145fe507f75e5430c375b3a85383ab29357/nodepool/elements/bindep-fallback.txt >
As announced, these two changes have now merged. Please don't
hesitate to let us know if you require any assistance working
through suspected fallout from either or both.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 963 bytes
Desc: not available
More information about the openstack-discuss