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

[Benoît Allard]

On 9/21/2011 4:48 PM, BRM wrote:
> ----- Original Message -----
>> From: Benoît Allard<benoit at aeteurope.nl>
>>>   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 ;)
>
> Where do I need to go to modify the master-slave protocol to add the QueryRegistry functionality?

First of all, you need to add the functionality to your slave. Don't 
think about the protocol yet.

This is the place where the commands are defined:

https://github.com/buildbot/buildbot/tree/master/slave/buildslave/commands

I suggest you add something like a windows.py file, your command there, 
register it to registry.py (which is not about the windows registry), 
increment the version number, and add some unit tests to check your 
functionality is running fine.

Here are the unit test for the other commands:

https://github.com/buildbot/buildbot/tree/master/slave/buildslave/test/unit

Then, we'll talk about the protocol and the visual studio steps ...

>
> I'll see what I can conjure up.
>

Wish you good luck ! Don't hesitate to report trouble, questions, ...

Ben.

-------------- 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/85f54f9c/attachment.bin>