We make (probably excessive) use of environment variables for paths to external libraries and such for our builds.
We had a developer add a new environment variable recently and the build broke, which we expected. We added it to the buildstation, but I don’t see that change reflected in Continua. Is there a way to trigger a refresh of the environment variables without stopping and restarting the service?
Hi Jeremy ,
We don’t currently have a way of refreshing environment variables without restarting the service. I can’t see any reason, however, why we should not be getting the user and system environment variables from the agent at the start of each stage and passing them to the process runner. I’ll look into implementing this.
Note that most several actions including MSBuild and FinalBuilder actions allow you to specific the environment variables to be sent to the process. We recommend doing this if possible rather than relying on environment variables set on the agent.