[Buildbot-devel] Changing the behavior of the SVN buildstep defaultBranch argument...

[Gav...]

> -----Original Message-----
> From: Dustin J. Mitchell [mailto:dustin at zmanda.com]
> Sent: Saturday, 27 March 2010 4:56 AM
> To: Gareth Armstrong
> Cc: buildbot-devel at lists.sourceforge.net
> Subject: Re: [Buildbot-devel] Changing the behavior of the SVN
> buildstep defaultBranch argument...
> 
> On Fri, Mar 26, 2010 at 1:05 PM, Gareth Armstrong
> <gareth.armstrong at hp.com> wrote:
> > Would folks like to see this become the default, or should legacy
> preside?
> > Thoughts and comments are more than welcome.  If feedback is positive
> I will
> > post a patch to github.  In any case, have a good weekend
> 
> My feeling is that this "defaultBranch" business is a bad idea - it
> causes confusion, and makes a lot of common configurations difficult.
> IMHO, a source step should just build the source stamp it was given --
> not try to take pieces of that source stamp and invent other pieces.
> 
> We now have source stamps specifying the source code completely:
> repository, project, branch, revision.  Sure, branch can be None, in
> which case you need to supply a default (this was a design mistake,
> IMHO).  And revision can be None, which means "latest" (this is very
> useful).
> 
> So I think that if we're going to change existing behavior, it should
> be in the direction of just building what you're told, rather than
> (and am I reading this right?!) making the defaultBranch *override*
> the branch in the SourceStamp.

This has prompted me to do that Blog post I promised Dustin some time ago:

http://blogs.apache.org/infra/entry/asf_buildbot_svn_setup

Applies to our 0.7.x setup, which may help Gareth, but as Dustin alludes to above, the 0.80 has nice
shiny new 'project' and 'repository' scheduler properties which may negate
the need for some of what I just blogged, but I'll find out shortly I guess ;)

Gav...

> 
> Dustin
> 
> --
> Open Source Storage Engineer
> http://www.zmanda.com
> 
> -----------------------------------------------------------------------
> -------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel