Hi everyone I got tired of managing our BuildBot(s), so I decided to switch our continuous integration tool to Jenkins (formerly known as Hudson). You find our Jenkins at http://gimptest.flamingtext.com:8080/ The main benefits are: * An order of magnitude easier to configure and maintain. All configuration happens through the web interface. * Has its own account and login system, no need for accounts on the host machine. * One Jenkins for all our projects vs one buildbot per project * Mails with last build log lines and list of changes since last build works out of the box. That is quite a bit of work to get working with buildbot, so much that I gave up on it. In a few days I will make failures be posted to gimp-developer, I think that is good to do if the mails contains logs and list of changes. The nightly tarballs can now be reached both through HTTP and FTP with permanent URLs: babl: ftp://gimptest.flamingtext.com/pub/nightly-tarballs/babl-git-master.tar.bz2 http://gimptest.flamingtext.com:8080/job/babl-distcheck/lastSuccessfulBuild/artifact/babl-git-master.tar.bz2 GEGL: ftp://gimptest.flamingtext.com/pub/nightly-tarballs/gegl-git-master.tar.bz2 http://gimptest.flamingtext.com:8080/job/gegl-distcheck/lastSuccessfulBuild/artifact/gegl-git-master.tar.bz2 GIMP: ftp://gimptest.flamingtext.com/pub/nightly-tarballs/gimp-git-master.tar.bz2 http://gimptest.flamingtext.com:8080/job/gimp-distcheck/lastSuccessfulBuild/artifact/gimp-git-master.tar.bz2 To simplify configuration, I wrote a simple 'GNOME Project Builder' Jenkins plug-in that can be found here: https://github.com/Enselic/gnome-project-builder Regards, Martin -- My GIMP Blog: http://www.chromecode.com/ "Nightly GIMP, GEGL, babl tarball builds" _______________________________________________ Gegl-developer mailing list Gegl-developer@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gegl-developer
