GNOME Bugzilla – Bug 695149
revive build.gnome.org as a unified status/reporting system
Last modified: 2013-11-21 14:56:07 UTC
Previously, build.gnome.org was using jhbuild-buildbot. Currently we have ostree.gnome.org as well as the Ubuntu-jhbuild bot: https://jenkins.qa.ubuntu.com/view/Raring/view/JHBuild%20Gnome/ I just got an offer for a PowerPC64 LPAR hosted in the OSUOSU to do builds/testing as well. Finally, we'll have mingw32 cross builds of gtk+. These are disparate build systems - but what would be nice is to have a basic unified reporting and control system. We'd have to figure out two fundamental things: 1) How do we feed data from outside the firewall to the page? push/pull? 2) Who is authorized to access and maintain the machines?
s/OSUOSU/OSUOSL/
There's a third thing that would be nice - a mechanism for these builders to get push notifications of commits. If we handed out a shared secret, that could also be used to access say a HTTP server running a websocket API.
Not just push notifications of commits - what I'd also like to do once we have this running is build and test patches submitted in bugzilla. So we need to ensure the API is "growable" to building many branches. We'd have build names like this: * master * gnome-3-8 * master-bug678922 * master-bug643843 * gnome-3-8-bug722980 etc.
Initial web page is up: http://build.gnome.org
The GNOME Infrastructure Team is currently migrating its bug / issue tracker away from Bugzilla to Request Tracker and therefore all the currently open bugs have been closed and marked as OBSOLETE. The following move will also act as a cleanup for very old and ancient tickets that were still living on Bugzilla. If your issue still hasn't been fixed as of today please report it again on the relevant RT queue. More details about the available queues you can report the bug against can be found at https://wiki.gnome.org/Sysadmin/RequestTracker. Thanks for your patience, the GNOME Infrastructure Team