[Buildbot-devel] Building tagged releases
oleg at smolsky.net
Sun Sep 9 18:02:03 UTC 2012
On 2012-09-09 10:41, Dustin J. Mitchell wrote:
> On Fri, Sep 7, 2012 at 2:23 AM, Oleg Smolsky <oleg at smolsky.net> wrote:
>> Hi there, I know that I can force a build using any existing builder and
>> wonder whether it is common to build tagged releases that way? It seems, I
>> would have to do something like this:
>> create a special builder for the release branch (with no schedule)
>> create a custom step to punch revision information into source files
>> build binaries and packages/installers
>> create a step to push packages/installers somewhere
>> Does this sound right? It so, is version information pushed in via
>> properties? How do I access it inside build steps?
> It sounds like you're on the right track. I'm not sure what you mean
> by version information, but yes, most likely that would find itself in
> properties. You get data from Properties using WithProperties,
> Property, or (in 0.8.7) Interpolate.
Hey Dustin, here is a concrete example of what I am looking to do:
- start with "v1" branch in Mercurial
- commit a few changes into the branch
- tag the tip of that branch as "build_50"
- initiate a build off that tag as "v1.0.6 build=50"
I have a script that writes these strings into a header file, so that
"--version" output of all binaries is consistent. The point here is that
I want to have version information outside of the source in order to
simplify merging. This lets me build multiple intermediate versions of
"1.0.6" just by specifying the tag: build_50, build_51, etc.
So, my question is two-fold:
a) does it make sense to produce release builds with BuildBot? (I
think it does, but do people actual do that? If not, why?)
b) how do I get the final installer/packages off the slave? (do I just
scp or use NFS?)
More information about the devel