Hi Kevin, is there specific reason, why scratch builds cannot do it? I met hard to reproduce issues in builds several times. I would prefer to analyse scratch builds instead of production builds.
Could for example just single per-user scratch build archive be stored for some short time? Might be just a day or so. It might be useful to add some tweaks and retry. Keeping previous scratch build is not needed, but ability to extract information from non-production builds seems vital to me. Keeping record of failed production builds, which will stay there forever, does not look good to me. Cheers, Petr On 2/11/21 8:27 PM, Kevin Fenzi wrote: > Greetings. > > We have enabled the koji 'save-failed-tree' plugin in > koji.fedoraproject.org. This plugin allows you to tell koji to bundle up > a failed official builds chroot (either partly or fully) and download it > to investigate it locally. > > This plugin should only be used for the case where you cannot determine > the cause of a build failure by any other means and need to examine > specific files in the chroot to do so. > > A few things to note: > > * This will only work on failed official builds that have failed > recently enough to still have their chroot on the builder where they > failed (default: 1 day) Not scratch builds. Not canceled builds. > The chroot downloads are REALLY LARGE. Please use this sparingly. > > * This will only work on buildArch tasks, not images, etc > > * Saved tree .tar.gz's are deleted from koji after 14 days. > > * You need to have python3-koji-cli-plugins subpackage installed to use > the command. > > * You run the command as: koji save-failed-tree <failed-taskid> > > I hope that this will be of use to help maintainers track down hard to > isolate bugs when all other means fail. > > kevin > > > _______________________________________________ > devel-announce mailing list -- devel-annou...@lists.fedoraproject.org > To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > > > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > -- Petr Menšík Software Engineer Red Hat, http://www.redhat.com/ email: pemen...@redhat.com PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB
OpenPGP_signature
Description: OpenPGP digital signature
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
