[Buildbot-devel] Strategy for highly branched codebase

[Ludovic Chabant]

Thanks everyone for the replies.

1. Philippe's "third" approach is not possible for us, because most of our
customers are not using buildbot at all, instead using their own build
infrastructure. So the "details on how to build" are specific to that
team's build system.

2. So the second strategy seems to be the most common.
Could we just add another source step with a different `workdir` to sync
the scripts in a directory next to the standard `build` directory? And then
have the normal build steps reference scripts in there? Are there any known
problems with this approach? Also, the documentation doesn't really tell
you if the `workdir` parameter for source steps is supposed to be relative
to the `build` dir or to the buildslave's base dir? (I could probably
figure that out by digging in the code but hey, while we're at it :) ).
Last, is there a way to get the buildslave's base dir from a build factory,
or do you have to use "../" in the ShellCommands?

Thanks,
--
   l u d o .
   . 8 0 17 80
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20130530/8eec63be/attachment.html>