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

BRM bm_witness at yahoo.com
Fri Sep 16 15:40:38 UTC 2011

----- Original Message -----

> From: Charles Lepple <clepple at gmail.com>
> To: BRM <bm_witness at yahoo.com>
> Cc: "buildbot-devel at lists.sourceforge.net" <buildbot-devel at lists.sourceforge.net>
> Sent: Friday, September 16, 2011 10:23 AM
> Subject: Re: [Buildbot-devel] BuildBot and Visual Studios...
> On Sep 16, 2011, at 9:53 AM, BRM wrote:
>>  (i) showed support for VC++ projects,
> http://buildbot.net/buildbot/docs/current/full.html#Visual-C_002b_002b
>>  or (ii) how to get projects going to start with, especially on Windows.
> http://trac.buildbot.net/wiki/RunningBuildbotOnWindows


I had see the second one, but it didn't make much sense to me as far as getting a build in. The first one really helps with that. Perhaps there should be a link in the second referencing the first? (Just a thought.)

>From: Philippe McLean <philippe.mclean at gmail.com>
>To: Charles Lepple <clepple at gmail.com>
>Cc: BRM <bm_witness at yahoo.com>; "buildbot-devel at lists.sourceforge.net" <buildbot-devel at lists.sourceforge.net>
>Sent: Friday, September 16, 2011 11:13 AM
>Subject: Re: [Buildbot-devel] BuildBot and Visual Studios...
>Our site has been using buildbot with great success since last winter. 
>Our slaves build with Visual Studio 2008 on Windows Server 2003 SP2 32 bit. Slaves are cloned vms.
>The master also runs on Windows Server 2003, though there is no compelling technical reason for placing it there.
>I based our setup on the wiki noted:

Good to know.

>There is one major pitfall I discovered related to Windows file system permissions inherited during python egg installation that is not noted on the wiki.
>I found that I had to do all the python setup and installation as the actual "Administrator" account, and not as another user with Administrator privileges,
>otherwise the windows service would silently fail.

Thanks. That will certainly save me some headaches when I go to set this all up.

>Running shell steps can sometimes lead to surprises with command line parameters. Avoid spaces and special characters.

Are there issues with spaces in the paths? Unfortunately, our source tree has things like "common source" in it. Can't get away from that for the time being. (Newer source trees avoid that; but the core products I'm doing this for are littered with it.)

Also, out of curiosity - has anyone used InstallShield with buildBot?

>good luck!

Thanks, I'm sure I'll need it.


More information about the devel mailing list