[Buildbot-devel] repository + Source steps

[Gav...]

> -----Original Message-----
> From: Dustin J. Mitchell [mailto:dustin at zmanda.com]
> Sent: Saturday, 10 April 2010 6:10 AM
> To: buildbot-devel list
> Subject: [Buildbot-devel] repository + Source steps
> 
> There have been a number of changes recently regarding Source steps
> and the repository attribute of a change/sourcestamp.  With apologies
> if I missed anyone, this has been mainly the work of Tobias Oberstein,
> Benoît Allard, and Marcus Lindblom.
> 
> However, I want to make sure I (and everyone reading this) understand
> what's going on here.
> 
> First, some time ago we added "repository" and "project" attributes to
> Changes and SourceStamps.  The repository attribute is intended to
> supply context for revision and branch, and the project is an
> arbitrary string that can designate the particular project being
> changed (whatever that means to the organization .. usually a
> particular codebase that requires a particular build process).
> 
> We also added the ability to flexibly filter on these attributes to
> all change-watching Schedulers (mostly Scheduler and
> AnyBranchScheduler).  That means you can set up a scheduler to listen
> for changes to a particular project, and start particular builders
> when those changes arrive.  It's multi-project support!  Hooray!
> 
> But very few people just want to build two completely independent
> applications in the same buildmaster.  Everyone's got their twist [*].
> 
> So, one handy thing is to have the *same* buildfactory be able to
> build multiple projects, which means that the Source steps should
> check out code from the repository in the SourceStamp.  But with the
> exising (0.7.12) configuration language, that was hard: we've always
> required that the repository be specified twice in the configuration,
> once in the ChangeSource, and once in the Source step.  So there are a
> number of recent changes so that a Source step will, if not given a
> repository explicitly, use the repository from the SourceStamp.  This
> last part is documented here:
> 
> http://github.com/djmitche/buildbot/commit/a9ab23bfaa7fa91e04f4f1c15451
> c1708777a90b
> 
> I would like to verify a few things, though:
> 
>  1. There are no behavior changes to Source steps for existing
> configurations
>  2. Which VC systems does this work with?
> 
> There are many more changes to be made.  Tobias is looking at how to
> build each project in a separate repository (I'll send a separate
> email about that).  There are lots of other changes on the horizon,
> too!
> 
> Dustin

Thanks for the explanations Dustin. This looks like it should fit well with
our multi project setup. Though we have it working well anyway, having it
do so 'out of the box' as it were will make for easier future upgrades etc..

Thanks also to those who worked on it. Good stuff!

Gav...

> 
> [*] And, I should note, in general everyone thinks that their twist is
> so self-evident that "everyone does it this way" and it should just be
> the default behavior.  Not so!
> 
> --
> 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