[Buildbot-devel] repository + Source steps

[Marcus Lindblom]

On 2010-04-09 22:10, Dustin J. Mitchell wrote:
> 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 [*].

Indeed. :)

My view of a project is (was?) it is what groups many pieces of software 
together, i.e. there might be many repos per project, as each software 
piece might have it's own repo. (I took the project literally as our 
trac instance, of which we might have more as our company grows.)

I'm thinking we might need some "überproject" later for a group of 
builds (akin to what you wrote on #789[1] yesterday). Currently I've 
thought about that as project and the discrete pieces of software built 
as something else again (modules for lack of better word (of which might 
be many in one repo, or one per repo)).

Is it just me? ;) ... or should we try to rename project -> module (or 
something equally generic) to free up "project" for the future? (Or 
decide what an "überproject" should be called right away. projectgroup?)

Mainly, I just want to be sure we get the terminology right and are 
clear about that in the docs and code when we launch this.

[1]: http://buildbot.net/trac/ticket/789#comment:2

Cheers,
/Marcus