[Buildbot-devel] repository + Source steps
Dustin J. Mitchell
dustin at zmanda.com
Sun Apr 11 19:00:48 UTC 2010
On Sun, Apr 11, 2010 at 12:13 PM, Marcus Lindblom <macke at yar.nu> wrote:
> 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)).
...
> 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.
Absolutely! So what you're describing is already encapsulated in the project.
Because "project" is so flexible, you can add hierarchical naming if
you'd like, e.g.,
$überproject/$module/$app/$project
or whatever you want to call the levels. You can then use regular
expressions or even a custom function to filter on project at the
scheduler level.
Your ideas regarding building *across* projects are good, but are not
covered by the current implementation, since we don't have good
equipment in place to correlate and coordinate multiple builds.
As for Tobias' bringing VC's into this: don't do that. The repository
is related to the VC. The project is only related to the
infrastructure of the organization running buildbot. For example, at
Zmanda, we have 6 projects, 5 of which are built from one repository,
and one from a different repository. We'll probably be using mixed
Git/SVN repositories at some point. Actually, several of our projects
are built from *several* repositories (build scripts from one repo and
source from another). So it gets complicated. But it's important to
not allow the VC structure to "bleed" into the project structure, at
least not in the design of Buildbot (you can do whatever you want in
your install!).
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
More information about the devel
mailing list