[Buildbot-devel] Step fails only under Buildbot

[Dan Kegel]

I had to give up on running buildbot in a venv, since that caused
builds that used system python packages to fail.

On Fri, Mar 7, 2014 at 11:26 AM, Na'Tosha Bard <natosha at unity3d.com> wrote:
>
> On Mar 7, 2014 8:19 PM, "Bob Hood" <bhood2 at comcast.net> wrote:
>>
>> On 3/7/2014 11:21 AM, Na'Tosha Bard wrote:
>>>
>>> 2014-03-07 18:35 GMT+01:00 Bob Hood <bhood2 at comcast.net>:
>>>>
>>>>
>>>> Any suggestions on how to figure out why the process fails when run
>>>> under
>>>> Buildbot but not from the CLI?
>>>
>>>
>>> Try running it from the CLI inside the buildbot virtual environment.
>>> I've had problems in the past with, for example, how Python upper-cases
>>> environment variable names.
>>
>>
>> Hey, Na'Tosha.
>>
>> Do you mean set up a Python virtual environment, or are you saying that
>> Buildbot provides such an enclosure?  A Google of "buildbot virtual
>> environment" didn't turn up anything edifying.
>>
>> Might you have a URL that provides more information on running it this
>> way?
>
> Hmm.  Maybe our slaves are set up weirdly, but to do this on our slaves, it
> would be:
>
> $ source ~/buildbot-venv/bin/activate
>
> The go to the appropriate directory and run the build.  The buildslave runs
> inside this virtualenv so there can be differences.
>
> Cheers,
> Na'Tosha
>
>
> ------------------------------------------------------------------------------
> Subversion Kills Productivity. Get off Subversion & Make the Move to
> Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually works.
> Faster operations. Version large binaries.  Built-in WAN optimization and
> the
> freedom to use Git, Perforce or both. Make the move to Perforce.
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel
>