[Buildbot-devel] Clean environment on build slaves

[Philippe McLean]

by definition this is slave environment specific so should come from outside
buildbot.
An easy way to manage it is to have startup script for the slave and run it
from both places (reboot/cron restart).

On Tue, Oct 11, 2011 at 1:26 PM, Greg Ward <greg at gerg.ca> wrote:

> On Tue, Oct 11, 2011 at 3:47 PM, Dustin J. Mitchell <dustin at v.igoro.us>
> wrote:
> > Probably the best solution is to start buildbot from a shell script
> > that sets the env explicitly.  You can also override all of the
> > "important" variables in every shell step, if that works better for
> > you..
>
> Yeah, but it'd be nice to have the same logic on Linux, OS X, and
> Windows. So we're going to try hacking something into buildbot.tac. If
> it's not too vile, we'll probably go with that. If it is, I guess
> we'll try a Python wrapper rather than a shell script.
>
> Thanks --
>
> Greg
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2d-oct
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20111011/4dd66e31/attachment.html>