[Buildbot-devel] perforce connection

William Deegan bill at baddogconsulting.com
Tue Aug 21 23:29:45 UTC 2012


On 08/21/2012 03:32 PM, Andrea Crotti wrote:
> On 08/21/2012 09:37 PM, William Deegan wrote:
>> Did you check the step log to see if the env variable shows up there?
>> And/or what the command line is?
>>
>> -Bill
>
> What do you mean in the step log??

Got to http://localhost:8010/waterfall and click on the failing step.
You'll see a log of the command line and the environment variables.

> I mean I am also passing the p4passwd, but to make sure I also did
>
> export P4PASSWD='mypass'
> buildbot restart
>
> and I even went with ssh on the manhole interface and yes, os.environ 
> shows the variable set..

That doesn't help your slave.
If you want a step to be executed with specific values in it's 
environment you should use the env argument to the step (from the manual 
http://buildbot.net/buildbot/docs/current/manual/cfg-buildsteps.html)

env
    a dictionary of environment strings which will be added to the child
    command's environment. The usual property interpolations can be used
    in environment variable names and values - see /Properties/
    <http://buildbot.net/buildbot/docs/current/manual/cfg-properties.html#properties>.



-Bill
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20120821/8a25b60f/attachment.html>


More information about the devel mailing list