[Buildbot-devel] Clean environment on build slaves

BRM bm_witness at yahoo.com
Fri Oct 21 02:29:46 UTC 2011

>From: Greg Ward <greg at gerg.ca>

>To: BRM <bm_witness at yahoo.com>
>Cc: Philippe McLean <philippe.mclean at gmail.com>; buildbot-devel <buildbot-devel at lists.sourceforge.net>
>Sent: Tuesday, October 18, 2011 9:53 PM
>Subject: Re: [Buildbot-devel] Clean environment on build slaves
>On Tue, Oct 18, 2011 at 12:54 AM, BRM <bm_witness at yahoo.com> wrote:
>> Or run the slave as a specific user that has its own environment settings -
>> settings that are managed and can be kept clean.
>> That can be done on any platform - OS X, *nix, and Windows.
>I already do that. The problem, as I explained in my original post, is
>that the environment the slave daemon has when started by cron
>(@reboot) is different from what it gets if I SSH to the slave and run
>"buildbot restart $slavedir". This is just a fundamental problem with
>cron vs interactive logins on Unix/Linux, and I was hoping BuildBot
>already had a good workaround.
>Sounds like it doesn't, so we've cobbled together a custom wrapper
>script. Seems to be working so far.

That is simply the nature of cron, and that is how cron is recommended to be operated - by putting the logic in a script and running it there, not by directly calling programs. Probably for that exact reason.



More information about the devel mailing list