[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [buckminster-dev] Hudson plugin and provisioning

Hi Flavio,

I installed Windows on a virtual box and configured it as a hudson slave to finally have my own testing environment for that.
Everything seems to work fine now on both the Linux host and the Windows slave (no cygwin installed). I've just released version 1.0.1 that contains the fixes. I hope it works better for you now.
The new version will show up as usual with a few days delay in your update center.


Thank you for all the help.

Best regards,
Johannes

Hi Daniel,

I just replied to Flavio in the other thread in the buckminster newsgroup:

"I installed Windows on a virtual box and configured it as a hudson slave to finally have my own testing environment for that.
Everything seems to work fine now on both the Linux host and the Windows slave (no cygwin installed). I've just released version 1.0.1 that contains the fixes. I hope it works better for you now.
The new version will show up as usual with a few days delay in your update center."


Same applies to you of course, thank you very much for the patch you sent me, the absolute paths finally did the trick.
I had to change a few things though (in case you are interested):
The directorScriptName and buckyScriptName do not work like that in a distributed build (Master/Slave).
The code is always executed on the master, therefore the methods would only return the correct script name if Master and Slave run the same operating system.
The trick was to make this kind of invocation over a VirtualChannel to have it executed on the current Build machine.
Other than that I took a similar approach like you in the patch you submitted, feel free to have a look at the code changes.


Best regards,
Johannes