Multiple sub projects in SVN

[Andy <trac@…>]

I've been using bitten for a number of years now and I'm very happy with the simplicity and the stability of the system. However, I now need to work out how I can configure Bitten to build a different directory structure in svn than what I normally use.

Within svn, all my current projects adopt the standard top level of trunk, tags and branches, but I'm now about to create an svn project database with multiple subprojects at the top level, all owned by individual developers, e.g.

+-root/
  +-project1/
  |  +-trunk/
  |  +-tags/
  |  +-branches/
  +-project2/
  |  +-trunk/
  |  +-tags/
  |  +-branches/
  +-project3/
  |  +-trunk/
  |  +-tags/
  |  +-branches/

Each project will be built with the same build script and all have to adopt the same directory structure, version scheme, test strategy etc... so apart from the name of the project, they all look identical to the build system.

For all standard svn projects, I typically have two build configs defined per Bitten system; one that builds trunk and the other that builds tags. I'd like to do the same for the svn with multiple sub projects, but without creating an individual build configuration for each identical project. Ideally, I'd like a scheme where Bitten can support a parameter in the build recipe that corresponds to the Trac component name, and this component name parameter can then be used as input to generate individual build configurations for all the components it discovers.

Maybe there's a simpler solution to my problem. Suggestions on how to do this with the current version of Bitten are more than welcome...

[hodgestar]

Will the repository path variable (see ​http://bitten.edgewall.org/wiki/Documentation/recipes.html) not allow you to do what you want?

It may be better to ask this on the mailing list (where more people will respond to it) than on the issue tracker (since it's not a concrete feature enhancement or bug really).

[Andy <trac@…>]

Good point! Apologies for the ticket spam - I'll use the mailing list. Please feel free to close this for now.

[anonymous]

Replying to Andy <trac@…>:

Good point! Apologies for the ticket spam - I'll use the mailing list. Please feel free to close this for now.

No problem! See you on the mailing list. :)