[Buildbot-devel] Standard practice with projects that try to modify .. ?

BRM bm_witness at yahoo.com
Tue Sep 25 20:17:53 UTC 2012

> From: Dan Kegel <dank at kegel.com>

>To: BuildBot Devel <buildbot-devel at lists.sourceforge.net> 
>Sent: Tuesday, September 25, 2012 2:37 PM
>Subject: [Buildbot-devel] Standard practice with projects that try to modify .. ?
>Hi ho.  This may be an FAQ, but:
>As far as I know, Buildbot puts the source in a 'build' subdirectory,
>and expects the darn project to not modify anything
>outside of that directory.
>What's the standard practice for dealing with projects that
>expect to be able to put files in .. ?
>e.g. when doing  "debuild" in the top of a source tree to build Debian
>packages, the .deb's end up in the parent directory.
>Do people do things like set workdir of the BuildFactory to

I had looked at something that way a while back - I had a project where I needed to pull in 4 or 5 different things in parallel to achieve a build.
See https://github.com/buildbot/buildbot/pull/253 for some details on how it was solved without changing buildbot; I suspect the same (or similar) kinds of solutions could be used for other VCS's.



More information about the devel mailing list