On 21/07/15 03:36, Jasper St. Pierre wrote: > > build.gnome.org <http://build.gnome.org> used to have auto builders > for jhbuild. >
Yes it was the jhbuild integration with buildbot, used on the old build-brigade times. > The problem is that jhbuild building requires maintenance. Everyone > I've talked to said that after a few months of trying to have a > jhbuild autobuilder, they gave up. > Yes, that was one of the reasons build brigade in the end was not successful. The idea would be putting jhbuild buildbot running, and as soon as it got stable, we could add the hooks to notify developers when someone is failing. The problem is that in most cases, build fails were not related to a (for example) wrong commit, but the usual jhbuild issues (those that for example Alberto is mentioning). So the outcome was that build.gnome.org with jhbuild buildbot required too much maintenance, and abandoned in the end. Current status with Continuous is far better. As Owen said, I would be worried to start to make changes on Continuous to be a jhbuild replacement, and going back to a build.gnome.org unmaintainable. > In my opinion, the way to fix this is to make jhbuild more like > Continuous. Have it read from the same manifest JSON format so that > when Continuous gets fixed, so do jhbuilds. Have it work automatically > in a similar way behind the scenes and "require less maintenance". And > perhaps, when possible, use poor prebuilt binaries from Continuous or > xdg-app. > > > On Mon, Jul 20, 2015, 6:28 PM Michael Catanzaro <[email protected] > <mailto:[email protected]>> wrote: > > On Mon, 2015-07-20 at 19:11 -0400, Owen Taylor wrote: > > 1) Hacking on system components that require hardware access > (kernel > > drivers, NetworkManager) > > 2) Hacking on system components that don't inherently require > > hardware access (kernel filesystems, systemd, polkit, gdm) > > 3) Hacking on session level components (gnome-session, gnome-shell, > > gnome-settings-daemon), and the libraries they use (gnome-desktop, > > clutter) > > 4) Hacking on libraries (gtk+) > > 5) Hacking on applications > > > > Which ones of these do you do? How do you do it? Is 'jhbuild run' > > sufficient for your needs? > > I do 4 and 5 with 'jhbuild build' et. al. and 'jhbuild run'. > > > Do you log into a jhbuild session? as yourself? as a test user? > > I used to do 3 on rare occasions, but stopped doing that because I no > longer remember how I ever managed to run a GNOME session under > jhbuild > in the past. There used to be instructions on the wiki, but they got > deleted at some point because they became outdated. The problems I > wanted to fix were never so urgent as to convince me to impel me to > figure it out on my own. Pretty sure new contributors have no chance > here. > > > Do you replace system level components? With 'make install'? By > > building packages? Do you use gnome-continuous? > > I've replaced system level components with 'make install' when I found > no other way to test a search provider. That displeased me. > _______________________________________________ > desktop-devel-list mailing list > [email protected] <mailto:[email protected]> > https://mail.gnome.org/mailman/listinfo/desktop-devel-list > > > > _______________________________________________ > desktop-devel-list mailing list > [email protected] > https://mail.gnome.org/mailman/listinfo/desktop-devel-list -- Alejandro Piñeiro ([email protected])
_______________________________________________ desktop-devel-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/desktop-devel-list
