Bamboo and script configured environment variables

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.

1 answer

1 accepted

2 votes
Accepted answer

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.

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

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Wednesday in Jira

Make your Atlassian Cloud products more secure: our NEW admin security guide

Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...

49 views 0 3
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you