Bamboo and script configured environment variables

[Mike Beeson]

Hi,

I am testing migrating our build from TeamCity to Bamboo. Our build steps include a script task at the start of the job to configure environment variables by calling 'C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\vcvarsall.bat', however the changes to environment variables when this is called do not appear to persist to subsequent tasks (ie. MSBuild ones), so our build fails.

Am I setting this up wrong? My MSBuild task builds a target that relies on the environment variables set from vcvarsall.bat.

Thanks,

Mike.

[Mike Beeson · Accepted solution]

For info, I solved this myself by creating an 'MSBuild.bat' file which sets up environment variables every time and calls MSBuild.exe. This then gets used by Bamboo to launch MSBuild rather than the executable.

Not a particularly nice solution imho.

[Robin Gauß]

I'm in the exact same spot two years later.