On 06/14/2017 04:16 AM, Martin Kolman wrote:
I agree with that - for example the Anaconda installer CI broke due
to
a rawhide package change in the last "working" compose. There is a
fixed package available and built in Koji, but it's not reaching the
Rawhide repos due to the broken composes. In this case we can fix the
CI by using a COPR build of the package, but in other cases it could be
more difficult.
BTW, when was the change to only release packages to repositories once
a compose succeeds introduced ? I kinda always thought packages go to
the Rawhide repos almost immediately - mirroring machinery permitting.
Rawhide has always been a daily compose of things that built in the last
day.
I'm not sure when the change to fail composes when blocking deliverables
failed landed. I want to say the Beginning of may, but I could be wrong.
Dennis should know more..
kevin