[arch-dev-public] Fwd: Arch Continuous Integration
Hi all, I just wanted everyone to know about this really useful tool. I think if we use it to ensure our packages are continuously buildable, rebuilds should become super simple and get more automated. I think this is something we need to bring on board as an official project at some stage! Allan -------- Forwarded Message -------- Subject: Arch Continuous Integration Date: Sun, 9 Nov 2014 15:40:43 -0800 From: Joel Teichroeb <joel@teichroeb.net> To: allan@archlinux.org Hi Allan, I've been working on developing a system that rebuilds all the packages in Arch automatically. It currently uses jenkins (https://jenkins.arch-ci.org) to do the package building and scheduling, with a custom written django frontend (https://arch-ci.org/). I'd be interested to get any feedback of how to make it useful to developers like yourself. Thanks, Joel
On 10.11.2014 12:37, Allan McRae wrote:
I think this is something we need to bring on board as an official project at some stage!
+1, I'd love to see this data get merged into our main site (especially a "not-building" table in the dev dashboard). To Joel: Only issue I've noticed so far is that multilib is apparently not enabled and therefore virtualbox, chromium and syslinux fail because they can't find lib32 dependencies. What kind of hardware backs this and how long does a full rebuild of all packages take? Apart from that, awesome idea and nice interface (maybe missing a maintainer filter, but you don't really have that data I guess). PS: I'm sending this to arch-general so discussion can continue on one list (if you want that).
On 11/11/14 00:16, Florian Pritz wrote:
On 10.11.2014 12:37, Allan McRae wrote:
I think this is something we need to bring on board as an official project at some stage!
+1, I'd love to see this data get merged into our main site (especially a "not-building" table in the dev dashboard).
To Joel:
Only issue I've noticed so far is that multilib is apparently not enabled and therefore virtualbox, chromium and syslinux fail because they can't find lib32 dependencies.
What kind of hardware backs this and how long does a full rebuild of all packages take?
Apart from that, awesome idea and nice interface (maybe missing a maintainer filter, but you don't really have that data I guess).
PS: I'm sending this to arch-general so discussion can continue on one list (if you want that).
I asked the build time earlier. Here is Joel's answer: "I have it record the build time for each package, so if I just add the average build times it gives around 6 days to build all the packages in core, extra, and community. That's for a single core build on one machine. I usually build multiple packages on each machine at once as a large portion of the time is often spent downloading sources. "
This is a very important initiative. However it may require trusted users to provide more build slaves for package rebuilds to be done in reasonable amount of time. I can provide one for example :) Once this is proved to work reliably I'd even suggest to remove raw access for uploading packages to prevent even theoretical sloppy mistakes. On Mon, Nov 10, 2014 at 4:34 PM, Allan McRae <allan@archlinux.org> wrote:
On 11/11/14 00:16, Florian Pritz wrote:
On 10.11.2014 12:37, Allan McRae wrote:
I think this is something we need to bring on board as an official project at some stage!
+1, I'd love to see this data get merged into our main site (especially a "not-building" table in the dev dashboard).
To Joel:
Only issue I've noticed so far is that multilib is apparently not enabled and therefore virtualbox, chromium and syslinux fail because they can't find lib32 dependencies.
What kind of hardware backs this and how long does a full rebuild of all packages take?
Apart from that, awesome idea and nice interface (maybe missing a maintainer filter, but you don't really have that data I guess).
PS: I'm sending this to arch-general so discussion can continue on one list (if you want that).
I asked the build time earlier. Here is Joel's answer:
"I have it record the build time for each package, so if I just add the average build times it gives around 6 days to build all the packages in core, extra, and community. That's for a single core build on one machine. I usually build multiple packages on each machine at once as a large portion of the time is often spent downloading sources. "
On Mon, Nov 10, 2014 at 8:16 AM, Florian Pritz <bluewind@xinu.at> wrote:
On 10.11.2014 12:37, Allan McRae wrote:
I think this is something we need to bring on board as an official project at some stage!
+1, I'd love to see this data get merged into our main site (especially a "not-building" table in the dev dashboard).
This is awesome. Does https://arch-ci.org/ provide any sort of JSON interface? We could add a snippet to each package page to go grab the build status, and as Florian hinted, being able to pull in dashboard-able data would be awesome. (Also, you're running your Django site in DEBUG=True mode, I wouldn't do that in production) To Joel:
Only issue I've noticed so far is that multilib is apparently not enabled and therefore virtualbox, chromium and syslinux fail because they can't find lib32 dependencies.
What kind of hardware backs this and how long does a full rebuild of all packages take?
Apart from that, awesome idea and nice interface (maybe missing a maintainer filter, but you don't really have that data I guess).
PS: I'm sending this to arch-general so discussion can continue on one list (if you want that).
participants (4)
-
Allan McRae
-
Dan McGee
-
Florian Pritz
-
Михаил Страшун