On Thu, Apr 20, 2017 at 12:17:10PM +0200, Stef Walter wrote:
Okay, that does explain some things. But I do have some follow up
questions:
1. Will Bodhi be modified so that failed tests can gate a bodhi update?
I guess it's doable, I do not know if bodhi's upstream is aware of this request.
I pointed him to this thread so he might chime in.
2. Will Bodhi be modified so that tests in progress can prevent a
bodhi
update?
Same as above
3. Will Bodhi be modified so that packages do not get into
updates-testing by merely creating a Bodhi update? As they do today?
Package won't go into updates-testing by themselves, packagers request it and
rel-eng does it.
So for all thre points above, maybe the right place to do this would be the
rel-eng tooling to prevent builds failing their tests to be pushed.
4. Will the CI pipeline and the Fedora Atomic host that it produces
be composed of some packages that are not yet in 'updates-testing'?
If I understood correctly Ari's pipeline, that is the case yes since (again,
iiuc) the package is built and the compose done from a dist-git commit, so
testing a different build from what is going to bodhi and then updates-testing.
5. How will the next run of the CI pipeline select the known good
set
of packages? Will it use updates-testing?
I'll defer this to the CI pipeline folks :)
6. Lastly, how does or might this work with rawhide?
If rawhide gets gated in bodhi (which is something I'm in favor of but needs to
go through other loops), then yes. Otherwise no since there would be no gating
point.
Pierre