[users at bb.net] Same workdir for two builders
buildbot at ryandesign.com
Sat Jul 30 23:08:23 UTC 2016
What about the documentation I quoted earlier, about setting a workdir function? I could write a workdir function that always returns the string "../build", right?
On Jul 30, 2016, at 4:33 AM, Pierre Tardy wrote:
> I dont think it is officially supported.
> Le ven. 29 juil. 2016 à 20:22, Ryan Schmidt a écrit :
>> Hi Pierre, thank you for your reply. I was trying to avoid having to specify the ".." path in every step. I was hoping there was a way to change the default workdir "build" to "../build". Is that possible?
>> On Jul 29, 2016, at 6:04 AM, Pierre Tardy wrote:
>> > Hi Ryan,
>> > What we usually recommend in order to implement builders that have a share directory is just to use ../ in your command.
>> > for example, if you need a shared virtualenv for all your builders you would say in your shell commands:
>> > SANDBOX=$WORDIR/../sandbox
>> > virtualenv $SANDBOX
>> > . $SANDBOX/bin/activate
>> > pip install foo
>> > etc.
>> > With this method, you assume that the workdir is always one directory away from your worker's main workdir (which is imho reasonable).
>> > Pierre
>> > Le ven. 29 juil. 2016 à 12:53, Ryan Schmidt a écrit :
>> >> Hi, I have several buildbot 0.8.12 worker machines, each with two builders. One of the builders ("watcher") is triggered by changes in the version control system. It does some preliminary setup work, then triggers one or more jobs on the other builder ("builder") which does the actual building. The "watcher" waits until all the jobs it triggered on "builder" have finished. I would like "watcher" and "builder" to share some files, and it seems natural to want to place those files in the workdir, which means they would need to share the same workdir. What's the best way to accomplish that, or is there a reason why I shouldn't do that? The most relevant documentation I found through Google was:
>> >> http://docs.buildbot.net/current/manual/customization.html#factory-workdir-functions
>> >> But that talks about using a callable function to return a workdir determined at runtime. I don't need that. How can I just set a different default workdir, for all build steps (while still allowing one build step to override that)? Can I just set build_factory.workdir to a string instead of a function? Is that documented somewhere that I missed?
More information about the users