[Buildbot-devel] Behavior expected from SVN master side source step

J Hegge qdev at oceanhills.net
Sun Apr 8 20:05:20 UTC 2012

On Apr 8, 2012, at 1:05 PM, Dustin J. Mitchell wrote:

> On Thu, Apr 5, 2012 at 11:01 AM, J Hegge <qdev at oceanhills.net> wrote:
>> Now, we do have a structure that is technically  <repo>/<branch>/<project> but that isn't the whole story.   Packaging releases makes for some messy work but I just use WithProperties to send amplifying data to steps.   My point is, I don't think changing to eliminate the strange repourl vs. baseurl bit matters, I'd rather just see it simplified.   I've not dug into the SVN code that I added for SVN tagging for some time but I remember scratching my head over the computeRepositoryURL() business.   Some of the magic code you are referring to?
> Can you tell a bit more about what you mean by "simplified"?

I was just referring back to the original email about using only one repository URL instead of two.  I tried to explain but perhaps not clearly, in my case I specify the URLs I need in each case.   One explicit URL is sufficient for my builds.  I don't know if that is sufficient for others but I was just offering some feedback. 

The oddity I face is a repository that contains Java servers/servlets along with binary clients (Android, iOS, OS-X, Windoze).  These clients are nested under a <project><client> dir structure.  CI builds for us just build a platform binary, the production builds package all together.   I could use multiple repos but well...

> It sounds like you have circumstances that are pretty complicated, and
> you mostly want Buildbot to not try to understand your circumstances,
> but get out of the way and do predictable things with the data you
> give it.  Is that about right?

Yes, complicated but not like source trees I've dealt with in the past where I was building DCE or CORBA binaries with Imake...  But to your point I've tried to keep complexity out of the Buildbot code, much as many previous emails from contributors have recommended.  A straightforward config and conservative use of WithProperties have kept my builds lean.   I try to contain the horror of Windows driver builds in its own box.  

Buildbot makes it rather easy to build across several languages, platforms and use tools like fabric, trial, boxgrinder and visual studio without having to specialize code for each, great tool. 

More information about the devel mailing list