On Sun, Nov 7, 2010 at 3:53 AM, Giampaolo Rodolà wrote:
> In such cases I would find more easy to be able to connect to the
> machine and test myself rather than create a separate branch, commit,
> schedule a buildbot run, wait for it to complete and see whether
> everything is "green".
>
> On the
Giampaolo Rodolà writes:
> In such cases I would find more easy to be able to connect to the
> machine and test myself rather than create a separate branch, commit,
> schedule a buildbot run, wait for it to complete and see whether
> everything is "green".
I agree with both Stephen and Martin's
On 11/6/10 10:53 AM, Giampaolo Rodolà wrote:
> Personally, I would find this particularly useful for OSX since it's
> one of the few OSes I can't manage to virtualize and which often
> causes me problems.
Although I said this on IRC, I'll repeat the offer to the list for those
not present -- I'm o
> sorry in advance if this sounds a little indiscreet, but I think it
> would be great if we'd have SSH access against some of the computers
> used to host buildbots.
The only way this can work is on a bilateral basis. If you need shell
access to one of the build slaves, contact the slave operator
Hi,
sorry in advance if this sounds a little indiscreet, but I think it
would be great if we'd have SSH access against some of the computers
used to host buildbots.
Personally, I would find this particularly useful for OSX since it's
one of the few OSes I can't manage to virtualize and which often
