[Buildbot-devel] Retrieving build results

Chris Leishman chris at leishman.org
Tue Nov 29 02:10:38 UTC 2005

On Mon, Nov 28, 2005 at 01:30:45PM -0800, Joel Becker wrote:
> 	Well, I'm not a buildbot developer, just a user.  I'm doing what
> I can to make do with the "all-the-world-is-one-repository" and so on.
> If buildbot starts providing me with this info on its own, then sure I
> don't have to do it in my Makefile.  I called the script
> "svnrev._guess_" for a reason :-)
> 	That said, I'm not sure where this functionality goes.  Our
> release numbers work very well for us, but might not work for others,
> and if you put the policy in buildbot, you remove flexibility.
> 	Discuss :-)

Hi Joel,

The question of where the release policy should be implemented is
interesting.  I can see arguments both ways - having it in the source is
good since it gives more flexibility, but the downside is that you can't
vary the release process independently of the source (eg. you can no
longer change the process used to make re-builds of old code, since the
process is part of the old code).

However, that's not really the point.  I was more arguing that there
should be a nice way to determine the attributes of the build without
having to use 'svn info' - it would be nice if the current branch,
VC revision and whether it is a 'try' build could be provided to the
build step somehow.  Maybe the changes and the try patch too?

You'd still have the choice to implement the release process in a script
in the checked out source (or elsewhere), but you wouldn't be dependant
on having the code checked out from subversion.


More information about the devel mailing list