Re: Suggestion: Continuous mass rebuild
On 07/29/2012 10:38 AM, Richard W.M. Jones wrote: Currently we're doing a mass rebuild about every couple of releases, ie. once a year. Since Dennis Gilmore has written this rebuild script already, why don't we run the script more or less continuously? Obviously we could pace the builds so they happen for each package about once a month and don't overload Koji. Then we track packages that don't build, say, 3 times in a row, and file FTBFS bugs for them and after that prioritize fixing them or kick them out of the distro. Rich. Matt Domsch used to do this on the side, which is the right way to do it. If he's not doing it anymore, I would urge some concerned contributor to help setup the infrastructure to do it again. -- Jesse Keating Fedora -- Freedom² is a feature! -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Suggestion: Continuous mass rebuild
On Mon, 30 Jul 2012, Jesse Keating wrote: On 07/29/2012 10:38 AM, Richard W.M. Jones wrote: Currently we're doing a mass rebuild about every couple of releases, ie. once a year. Since Dennis Gilmore has written this rebuild script already, why don't we run the script more or less continuously? Obviously we could pace the builds so they happen for each package about once a month and don't overload Koji. Then we track packages that don't build, say, 3 times in a row, and file FTBFS bugs for them and after that prioritize fixing them or kick them out of the distro. Rich. Matt Domsch used to do this on the side, which is the right way to do it. If he's not doing it anymore, I would urge some concerned contributor to help setup the infrastructure to do it again. There's been a lot of work to make it so we can do it ourselves. If anyone wants to help out on it I can point you to what we built. Until we get the new hw active we will be limited on where we can run, though. -sv -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Suggestion: Continuous mass rebuild
On 07/30/2012 12:02 PM, Seth Vidal wrote: On Mon, 30 Jul 2012, Jesse Keating wrote: On 07/29/2012 10:38 AM, Richard W.M. Jones wrote: Currently we're doing a mass rebuild about every couple of releases, ie. once a year. Since Dennis Gilmore has written this rebuild script already, why don't we run the script more or less continuously? Obviously we could pace the builds so they happen for each package about once a month and don't overload Koji. Then we track packages that don't build, say, 3 times in a row, and file FTBFS bugs for them and after that prioritize fixing them or kick them out of the distro. Rich. Matt Domsch used to do this on the side, which is the right way to do it. If he's not doing it anymore, I would urge some concerned contributor to help setup the infrastructure to do it again. There's been a lot of work to make it so we can do it ourselves. If anyone wants to help out on it I can point you to what we built. Until we get the new hw active we will be limited on where we can run, though. -sv I believe I misphrased my statement above. I'm not necessarily encouraging somebody to go outside the Fedora Infrastructure to do mass rebuild attempts. My goal was to encourage people to do it in a throw-away method, not an actual spec committing build bumping use of Koji. The rebuilds should be attempted outside of koji and without modifying the sources. If there is room to do that inside Fedora's Infrastructure, all the better. -- Jesse Keating Fedora -- Freedom² is a feature! -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Suggestion: Continuous mass rebuild
On Mon, Jul 30, 2012 at 9:46 PM, Dan Horák d...@danny.cz wrote: Richard W.M. Jones píše v Ne 29. 07. 2012 v 18:38 +0100: Currently we're doing a mass rebuild about every couple of releases, ie. once a year. Since Dennis Gilmore has written this rebuild script already, why don't we run the script more or less continuously? Obviously we could pace the builds so they happen for each package about once a month and don't overload Koji. Then we track packages that don't build, say, 3 times in a row, and file FTBFS bugs for them and after that prioritize fixing them or kick them out of the distro. please keep in mind that the resources available to secondary arches are limited and can't undergo the load the mass rebuild generate. They can follow the normal load of builds coming from primary for rawhide and updates for 2 released versions, but such peaks are way above the capacity. What takes 4 days in primary koji with dozens of builders it takes 2 or 3 weeks in secondaries (ppc, s390) with other work mostly stopped ... I agree with this as we experience this with ARM as well. That said the proposed scratch rebuilding in parallel (without committing to git) is something I applaud from a secondary arch PoV as a lot of the build issues I experience on secondary are actually also FTBFS on Primary when I test it further due to some other chance since the build was done so this will get more attention to those issues and help secondary arches greatly as it will be easy to tell if there's a known problem on primary. Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Suggestion: Continuous mass rebuild
Richard W.M. Jones rjo...@redhat.com writes: Currently we're doing a mass rebuild about every couple of releases, ie. once a year. Since Dennis Gilmore has written this rebuild script already, why don't we run the script more or less continuously? Obviously we could pace the builds so they happen for each package about once a month and don't overload Koji. Then we track packages that don't build, say, 3 times in a row, and file FTBFS bugs for them and after that prioritize fixing them or kick them out of the distro. I don't think we should do this exactly like a regular mass rebuild: it would create useless churn in the package set, specfile changelogs, etc. What would be useful is to do scratch rebuilds on this sort of schedule, without changing anything in git, and file bugs anytime a rebuild fails. That is more or less what Matt Domsch used to be doing; now that he seems to have stopped, I agree that it would be a good thing for the Fedora project to start doing it officially. regards, tom lane -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Suggestion: Continuous mass rebuild
On Sun, 29 Jul 2012, Tom Lane wrote: Richard W.M. Jones rjo...@redhat.com writes: Currently we're doing a mass rebuild about every couple of releases, ie. once a year. Since Dennis Gilmore has written this rebuild script already, why don't we run the script more or less continuously? Obviously we could pace the builds so they happen for each package about once a month and don't overload Koji. Then we track packages that don't build, say, 3 times in a row, and file FTBFS bugs for them and after that prioritize fixing them or kick them out of the distro. I don't think we should do this exactly like a regular mass rebuild: it would create useless churn in the package set, specfile changelogs, etc. What would be useful is to do scratch rebuilds on this sort of schedule, without changing anything in git, and file bugs anytime a rebuild fails. That is more or less what Matt Domsch used to be doing; now that he seems to have stopped, I agree that it would be a good thing for the Fedora project to start doing it officially. And we've been making progress on doing this - however we had to make sure we had sufficient builder systems and a way to quickly redeploy them. That's what I've been working on: https://fedoraproject.org/wiki/User:Skvidal/BuildSystem -sv -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
