Re: runroot changing during the course of a rawhide pungi run
On 02/26/2018 04:59 PM, Dusty Mabe wrote: > > > On 02/26/2018 07:51 PM, Kevin Fenzi wrote >> 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. > > Yeah there is more control over bodhi, which is good. What about branched > composes? It depends on if bodhi is enabled for it yet. Right now, branched f28 is like rawhide, next week when we hit bodhi enablement it will be like stable releases. kevin signature.asc Description: OpenPGP digital signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: runroot changing during the course of a rawhide pungi run
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 02/26/2018 07:51 PM, Kevin Fenzi wrote: > 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? Yeah the buildroot (since that is where the runroot installs packages from). > >> 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 kind of unfortunate because a developer could torpedo a pungi run 8 hours in. > > 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. Yeah there is more control over bodhi, which is good. What about branched composes? Dusty -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEPb6zG5c6sV89tRYPMwLb1zlS5nEFAlqUrX8ACgkQMwLb1zlS 5nGmXRAA332NcrKhpJkAEkst2XHTAknWtrvEgLl0SRTsD6vB7b6ndxmX4Uq1w4eu 44wSPzsI2KEkslEEktxdlS5tTtGOs2ogNzDZD0JWp013uWOvxYsYF84/qq/Cv7cT re67+HA0sdHKvZ4+BRwOcEtzzqqPbZmWbOssT3Zn4eOtxuZD1W19zsXwCdMl9tc6 vz1G5SO5Refj0jE19R9sHccRUv3+6QFagwiWW/tCE1kgo/qmbbIcgSwKzRIAkWhX rTgjNABJ6Q40wWrPyU0HgT5kzl6+htPgo7r4JlGyk7Kqo9OkaeN2jdCyn3tsQRJX TDr+kY2yh/IPtUegp0ULQuU/+QhxMG98GmmqiFIufniJPe3uySJYSlXSnuwe/P0L 5zfx89GL5YE2lfPM7mtnqnYJtpzYD6UyHKNUNRE1HKbZvdlM3vB/QfvQLQWcKXkB KFkLM53p3JqEvAJy4QnKsK4/w3zP9h9oDZ/r3DMyT8ECejwY6jP7pNwuAh6ADObT 6ZmRi091cbynveEmJX2aEsEVb6cWqbSbxwiba7JMwMHOW9ERtBAeLzH5dtze7Eie 4y8HYHC3GGsbPDc5M2uKZ7T6XcZdxKtxQ8VmOtBA1Gjvc3uxCeg/4ywae/ldkaO0 lZjMFyhvsx3qZKuqpQqwrxdGFd30nUVMo1bHUMfUx1QGDitvo+0= =5UWC -END PGP SIGNATURE- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: runroot changing during the course of a rawhide pungi run
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 signature.asc Description: OpenPGP digital signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
