I'm having some issues with environment variables not being properly set when executing a plan that runs on a Windows 10 agent. Specifically, when I remote into the agent and test the build scripts I've set up, the environment variables don't match the results of an echo when running my plan.
I'm using cmake and cl.exe to build our project. For the compilation step, I've configured a "script task" that runs with cmd.exe. At the beginning of the script, I initialize the command line build environment by calling vcvars64.bat. This initializes a number of environment variables that are necessary for the build to succeed (%PATH%, %LIB%, %LIBPATH%, %INCLUDE% to name a few). My issue is that the environment variables don't match the results of my remote session when I call vcvars64.bat from the script task (confirmed via echo). Does anyone have any ideas as to why I am seeing this inconsistency? I would prefer to not have to manually set these environment variables as the vcvars64.bat script is supposed to automatically set them.
NOTE: I'm running the bamboo remote agent as a service, and I've ensured that it is running as the "bamboo" user as opposed to the "system" user.
G’day Bamboo customers, Bamboo DC 8.1 is now available with it the following features and programs: SAML 2.0, OpenID Connect, and Crowd SSO In order to help admins with a simplified user manage...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events