layout | title | description | date | author | keywords | categories | index-image-url | index-image-alt |
---|---|---|---|---|---|---|---|---|
post |
Introducing Global Environment Variables |
Quick intro of Snap's global environment variables feature. |
2015-07-31 |
Fernando Junior |
snap ci, environment variable, global commands, continuous integration, continuous delivery, pipeline stages, build configuration |
features announcements |
screenshots/global-environment-variables/global-environment-variables-index.png |
Snap Global Environment Variables |
Back when we developed pinned commands, our main goal was to avoid repeated work for our users when they needed to run commands like bundle install
, npm install
or gradle build
on every stage.
When it comes to environment variables, the situation was quite the same. Some variables, like service's credentials, are also eligible to be used repeatedly. To do that, one would have to go through all stages and add individual variables on each and every one.
Not anymore.
![global environment variable example]({% asset_path screenshots/global-environment-variables/global-environment-variables.png %}){: .screenshot .big}
We are glad to announce that you can now pin such variables just like any command. This has long been requested and we hope that it makes managing build configuration easier for users.
More details can be found on our docs.
Snap CI © 2017, ThoughtWorks