[Buildbot-devel] BuildBot & Visual Studios....

Benoît Allard benoit at aeteurope.nl
Wed Sep 21 11:06:31 UTC 2011

On 9/20/2011 6:23 PM, BRM wrote:
> Just wanted to bring up a bug for discussion. I'm not familiar enough
> with Buildbot's protocols/etc to tackle it myself at present, and any
> support for InstallShield will likely need to follow the same kind of route.
> http://trac.buildbot.net/ticket/2108
> I finally got to the point of testing a build, and it failed because
> Buildbot had the incorrect path for VisualStudios, namely because the
> path was hard coded. Microsoft provides the required paths in some nice
> registry keys that we can access via Python - via either the
> _winreg/winreg built-in modules, or via PyWin32's win32api module. I
> reported the paths I know about in the bug.
> What I am curious about is how this would play out in build-master/slave
> architecture since the VisualStudios may not be installed at all on the
> build master, and/or different from the build slaves (even the build
> slaves could potentially be different from each other). For example, I
> am thinking of potentially moving my build master to a Linux computer at
> some point, and if I added another Windows computer for doing builds on
> it won't likely have the same installation path as the one I currently
> am using.
> For now, I can probably work around it using the "installdir" parameter.
> However, it would be very helpful for me (and likely others) to use the
> registry method in the bug report.

The main trouble over there is that you need to run some actions on the 
slave to know the right path. This is not something the current 
architecture easily allow you to do. The slaves have a set of 
capabilities, namely commands, and can't do anything for the master 
beside that.

For this to be possible, you need:

1. Add a command on the slave like "QueryRegistryValue" or such
2. Invoke that command from the vstudio steps (which runs on the master)
3. use the return value to update the settings sent during the actual
    invocation of devenv.

Nothing impossible, patch welcomes ;)


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4936 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://buildbot.net/pipermail/devel/attachments/20110921/cd6d0b69/attachment.bin>

More information about the devel mailing list