On 02/22/2018 07:34 PM, Dusty Mabe wrote: > > If I understand correctly there was a new lorax build [1] that completed > at 01:11 UTC (02/23) that then made it into the runroot of a task [2] that > was part of a pungi compose [3] that started at 14:54 UTC (02/22). runroot is confusing here as we have a koji plugin called runroot that runs tasks in a chroot. I think you mean buildroot here? > I think this caused problems with the build, but that isn't really > important. The real question is: if our runroot changes during the run then > we could have some tasks (lorax imagebuild etc) that run with some versions > of software and other tasks that run with others. This is probably especially > maddening when trying to debug why one failed when others didn't. > > Is my understanding correct? Yes, the rawhide buildroot is updated as soon as builds complete and are signed (plus a small time for the newrepo to run). This is not the case with any of the bodhi enabled releases. They only update the buildroot from base packages + stable updates + specific packages that are added as buildroot overrides. kevin
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
