[Buildbot-devel] build properties ...

[John Pye]

>
>
>Each build now has a set of named "Build Properties", which can be set by
>steps and interpolated into ShellCommands. The 'revision' and 'got_revision'
>properties are the most interesting ones available at this point, and can be
>used e.g. to get the VC revision number into the filename of a generated
>tarball. See the user's manual section entited "Build Properties" for more
>details.
>

Nice one! Thanks guys! This was just what I was wanting a few days back.

Cheers
JP


Steve Greenland wrote:

>On Wed, May 24, 2006 at 09:43:20AM -0700, Brian Warner wrote:
>  
>
>>I don't know of a good solution or tool to manage this process. My intention
>>is to have the user's manual be the primary place where users can learn how
>>to use the buildbot, but the user's manual is a lot younger than the rest of
>>the code, so there are places where the primary documentation is still in the
>>docstrings. And even after e.g. Waterfall has been documented in
>>buildbot.texinfo, I'm loathe to delete the docstrings, because that's where a
>>pydoc-using python programmer (as opposed to the User's Manual-using, er,
>>user) would think to look for them. Really I want a way to have the
>>docstrings get interpolated into the user's manual in the right page, so I
>>only have to maintain one copy of those docs.
>>
>>Any ideas?
>>    
>>
>
>I've lately been using ReStructured Text and the docutils tools for
>local documentation, to generate PDF, HTML, and text versions of the
>docs. RST is a minimal markup format -- easy to read and use in the raw,
>but capable of generating nicely formatted docs.
>
>It's intended for use in Python docstrings as well as standalone docs.
>
>You might start at http://docutils.sourceforge.net/docs/index.html for
>more info.
>
>Steve
>
>
>  
>