Re: [Gimp-developer] Nightly builds with buildbot, where can we host?

2010-09-07 Thread Emil Assarsson
Hi,

How about letting this buildbot approving commits in some way?
http://wiki.hudson-ci.org/display/HUDSON/Gerrit+Plugin

--
Emil


On Tue, Sep 7, 2010 at 7:56 AM, Martin Nordholts ense...@gmail.com wrote:
 On 09/06/2010 10:02 PM, Sven Neumann wrote:
 On Mon, 2010-09-06 at 21:38 +0200, Martin Nordholts wrote:
 On 09/06/2010 09:22 PM, Sven Neumann wrote:
 Will buildbot build failures be posted to this list? Do you have the
 'blame' feature setup so that the commits that potentially broke the
 build are listed?

 I think posting failures to the list would create too much spam, my plan
 was to have an IRC bot for that instead.

 Hmm, buildbot has support for that, but I don't quite understand what
 buildbot output on IRC would be good for. IMO the buildbot web-site
 should be accessible by anyone and the bot should send mails in the case
 of a build failure. Given how seldom the GIMP tree does not compile,
 this shouldn't create too much traffic.

 Well, mails would not only be sent in case of compile failure but also
 in the case of make distcheck failure, which is quite easy to break. But
 we can certainly try and see how it plays out.

  / Martin


 --

 My GIMP Blog:
 http://www.chromecode.com/
 Automatic tab style and removed tab title bar
 ___
 Gimp-developer mailing list
 Gimp-developer@lists.XCF.Berkeley.EDU
 https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer




-- 
Emil
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Nightly builds with buildbot, where can we host?

2010-09-07 Thread Martin Nordholts
On 09/07/2010 06:26 PM, Emil Assarsson wrote:
 Hi,

 How about letting this buildbot approving commits in some way?
 http://wiki.hudson-ci.org/display/HUDSON/Gerrit+Plugin

My employer uses Hudson and I considered using Hudson for GIMP too. 
Automatically building and testing commits before they are merged to 
master is a really neat thing to do.

But I chose buildbot over Hudson because

* buildbot is more readily available than Hudson, for example, Fedora 13 
does not have Hudson packages
* buildbot is built on Python, which is less controversial in terms of 
software freedom than Java (Personally I'm fine with both, but it can 
still matter to some)
* I already knew Hudson and wanted to learn buildbot
* I feared that people would look at Gerrit+Hudson as an obstacle, since 
commits needs to be submitted, it's not enough to just push

And now that I've experimented with buildbot a bit, I have ended up 
liking the system, so I don't plan to switch over to Hudson

  / Martin


-- 

My GIMP Blog:
http://www.chromecode.com/
Automatic tab style and removed tab title bar
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


[Gimp-developer] Nightly builds with buildbot, where can we host?

2010-09-06 Thread Martin Nordholts
Hi,

I have been experimenting with setting up nightly builds of babl, GEGL 
and GIMP using buildbot. Actually, it's morning builds, since the 
morning is the least common time on the day we push commits. I am now in 
a state where this works pretty well:

  * Each morning buildbot pulls the latest changes from git, does
a make distcheck, and copies to the resulting tarball to a
central directory along with the md5 sum

The benefits should be obvious but I'm listing a few of them anyway for 
clarity:

  * We can do development releases whenever we want, there will
always be a tarball ready to be released. In the past, getting
ready for a development release has taken weeks some times.

  * Since our automatic tests are continuously run, regressions will
be quickly discovered when tests exists, making it easier to
act upon them.

  * People will be able to easily test bleeding edge code without
having to wait for a release, assuming we publish the tarball
directory somewhere

I don't have a fixed IP address however which makes it hard for me to 
host a machine for this. So the question is: what alternatives do we 
have? Maybe this would be a good thing to spend our money on? I guess 
the easiest thing would be to rent a (possibly virtual) machine 
reachable from the internet. We can then add links to that machine on 
gimp.org to the tarball dir it produces.

Any thoughts?

Regards,
Martin


-- 

My GIMP Blog:
http://www.chromecode.com/
Automatic tab style and removed tab title bar
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Nightly builds with buildbot, where can we host?

2010-09-06 Thread Sven Neumann
On Mon, 2010-09-06 at 21:22 +0200, Martin Nordholts wrote:

   * We can do development releases whenever we want, there will
 always be a tarball ready to be released. In the past, getting
 ready for a development release has taken weeks some times.

That's over-exaggerating things a little. It has sometimes taken hours
to fix 'make distcheck'. By running this more regularly this can of
course be much improved.

Will buildbot build failures be posted to this list? Do you have the
'blame' feature setup so that the commits that potentially broke the
build are listed?

 I don't have a fixed IP address however which makes it hard for me to 
 host a machine for this. So the question is: what alternatives do we 
 have? Maybe this would be a good thing to spend our money on? I guess 
 the easiest thing would be to rent a (possibly virtual) machine 
 reachable from the internet. We can then add links to that machine on 
 gimp.org to the tarball dir it produces.

Well, we could ask if it is possible to have this run on cube. But I
guess that it really makes sense to have a dedicated (virtual) machine
for this.


Sven


___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Nightly builds with buildbot, where can we host?

2010-09-06 Thread Martin Nordholts
On 09/06/2010 09:22 PM, Sven Neumann wrote:
 Will buildbot build failures be posted to this list? Do you have the
 'blame' feature setup so that the commits that potentially broke the
 build are listed?

I think posting failures to the list would create too much spam, my plan 
was to have an IRC bot for that instead.

I don't have the blame feature set up yet, but is is usually not hard to 
figure out what commit that caused make distcheck to fail. Eventually I 
want to run make distcheck for each commit pushed, but we can live 
without that for now.


 I don't have a fixed IP address however which makes it hard for me to
 host a machine for this. So the question is: what alternatives do we
 have? Maybe this would be a good thing to spend our money on? I guess
 the easiest thing would be to rent a (possibly virtual) machine
 reachable from the internet. We can then add links to that machine on
 gimp.org to the tarball dir it produces.

 Well, we could ask if it is possible to have this run on cube. But I
 guess that it really makes sense to have a dedicated (virtual) machine
 for this.

I think so too, seems unnecessary to introduce security issues like this 
on cube. So, how do we go about getting ourselves a virtual machine? I 
rent one myself and then show receipts?

  / Martin


-- 

My GIMP Blog:
http://www.chromecode.com/
Automatic tab style and removed tab title bar
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Nightly builds with buildbot, where can we host?

2010-09-06 Thread Martin Nordholts
On 09/06/2010 10:02 PM, Sven Neumann wrote:
 On Mon, 2010-09-06 at 21:38 +0200, Martin Nordholts wrote:
 On 09/06/2010 09:22 PM, Sven Neumann wrote:
 Will buildbot build failures be posted to this list? Do you have the
 'blame' feature setup so that the commits that potentially broke the
 build are listed?

 I think posting failures to the list would create too much spam, my plan
 was to have an IRC bot for that instead.

 Hmm, buildbot has support for that, but I don't quite understand what
 buildbot output on IRC would be good for. IMO the buildbot web-site
 should be accessible by anyone and the bot should send mails in the case
 of a build failure. Given how seldom the GIMP tree does not compile,
 this shouldn't create too much traffic.

Well, mails would not only be sent in case of compile failure but also 
in the case of make distcheck failure, which is quite easy to break. But 
we can certainly try and see how it plays out.

  / Martin


-- 

My GIMP Blog:
http://www.chromecode.com/
Automatic tab style and removed tab title bar
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer