[Buildbot-devel] BuildBot and Visual Studios...
Philippe McLean
philippe.mclean at gmail.com
Fri Sep 16 15:54:50 UTC 2011
>
>
> >> (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
>
> Thanks!
>
> 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.)
>
Once past the installation, running the master.cfg is not much different
than other platforms except for paths and escaping.
Here is an excerpt from my master.cfg:
from buildbot.steps.vstudio import VC9
...
config='Debug'
branch='branches/release/37.0'
...
factory.addStep(source.SVN(mode='update', baseURL='svn://builder/IN/',
defaultBranch=branch, always_purge=False, doStepIf=DoNotPurge,
name="incremental update"))
factory.addStep(VC9(projectfile="IN\\IN.sln",
config=VC9BuildConfig(config), mode="build", description="compiling %s" %
config, descriptionDone="compile %s" % config, name="compile %s" % config,
haltOnFailure=True))
>
> >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.
>
I updated the wiki page with this information.
>
> 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.)
>
Paths with spaces are always an issue with scripting on any platform, but
they can be escaped with \\.
VC config like 'Win32|Any CPU" needs to be escaped as: "Win32^|Any CPU"
Avoid using bat and cmd for anything non trivial. Use python for scripting.
> Also, out of curiosity - has anyone used InstallShield with buildBot?
>
>
No, but it should be straightforward -- installshield can be invoked from
the command line.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20110916/a831ff21/attachment.html>
More information about the devel
mailing list