Lieven Govaerts writes:
> 6. I'm not going to activate the option to send mails to committers who make
> the build fail :)
Ha, why not? :-)
Seriously, we could maybe arrange for some notification to the
breakage@list. 'cause I'm not going to poll a web page for this info.
> 7. I've installed a TryScheduler as well. The TryScheduler is used to
> trigger manual builds, with custom patches not yet committed to the svn
> repository: "What would happen if I committed this patch right now?".
> To use the TryScheduler, developers need the buildbot client and a
> username/password to connect to the buildmaster.
This sounds like one of the most useful features of this system.
> There are some problems still in this area, to name a few:
> - 'buildbot try' uses svn diff on the local working copy to calculate the
> patch compared to current trunk. I tried it with my patch for issue #2475,
> which adds a new python test path_tests.py. The TryScheduler checkouts trunk
> and applies the patch, but in this example it fails to make the
> path_tests.py executable, so the test won't run. Since svn diff cannot
> express propset svn:executable I'll have to find out a workaround.
This should be rare enough that we could live with it if it turns out
to be hard to fix.
> - current setup only tests getting code from a branch, would be nice to have
> a builder which accepts release (candidate) packages to build and test those
> on multiple slaves.
Since the release branch and the tag are typically identical for some
time, this doesn't seem like a showstopper either.
> If anyone is interested in this buildbot configuration, please let me know.
> I'm willing to spend the time to make this solution work for the Subversion
> project. If it doesn't work in the end, atleast you get a better
> understanding on the requirements of the Build & Test Farm.
This all sounds very great! I currently run nightly tests for
1.3.x. It would be nice to try being a slave for all trunk and other
active branches as well. Where do I find out how to set up a slave?
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Mar 20 22:05:43 2006