[Buildbot-devel] New Source Steps
Charles Lepple
clepple at gmail.com
Wed Aug 17 13:03:50 UTC 2011
On Aug 17, 2011, at 8:56 AM, Charles Lepple wrote:
> On Aug 16, 2011, at 11:04 AM, Dustin J. Mitchell wrote:
>
>> On Thu, Aug 11, 2011 at 3:44 PM, Pradeepkumar Gayam
>> <in3xes at gmail.com> wrote:
>>> I have been working to move source steps to master and fix their
>>> behavior.
>>> So far Git, Mercurial, SVN and CVS are merged into master. I am
>>> hoping to
>>> get bzr merged by the end. Till now I used only Git and mercurial.
>>> I used
>>> SVN or CVS only for source step testing. So, I am expecting some
>>> 'gotcha's
>>> in the code. I can't find them on my own. It would be great of any
>>> users
>>> give a try and report back.
>>> documentation for new
>>> steps: http://buildbot.net/buildbot/docs/latest/cfg-buildsteps.html#module-buildbot.steps.source
>>
>> I haven't heard any reports back about success or failure with
>> these new steps.
>>
>> We're nearing the 0.8.5 release, and it would be great to give them
>> some exercise before that release is made.
>
> The buildbot instance where I can most easily try this is currently
> running 0.7.12, so I'm doing a bit more reading of the documentation
> than I would for the 0.8.2 buildmaster.
>
> If I am reading this correctly, I would basically change
> buildbot.steps.source.SVN to buildbot.steps.svn.SVN, and adjust the
> options as appropriate?
>
> If the old steps will be kept for compatibility, it might be good to
> clarify the name mapping in the documentation so that people can see
> at a glance which version they are using. I might have some time to
> work on this tonight, but any input would be appreciated.
>
> I like the look of the new Sphinx documentation, btw. Lightweight
> markup like RST and AsciiDoc makes it easier to read the source text
> IMHO.
Along these lines, the new source step documentation uses "..
py:module:: buildbot.steps.source" where most of the old documentation
uses ":class:buildbot...". The former is the only entry in the Sphinx
module list - is there a plan to migrate towards one or the other?
More information about the devel
mailing list