September 28, 2016
Introducing: Environment Variables
We’ve been listening carefully what our users need to help them automate their work. What we’ve found out is that developers want a possibility to use variables all over the pipelines without having to copy & paste the same values like maniacs.
That’s why we’re introducing Environment Variables.
What Environment Variables are for?
Variables are pairs of key-value. Once defined, you can use them in Buddy UI in the following places:
- In commands section of SSH actions
- In commands section of Build actions (Run Docker containers to execute commands)
- In every action field (ex: hostname, login, password, path)
The most popular use case is it to use them for authentication credentials. In that case, you prevent yourself from providing sensitive details in your scripts.
Also it’s a time-saver. Once something changes, you need to update just one thing in a central place instead of dozens of action settings here and there.
How to use them?
To define a variable go to Workspace Preferences (on the Dashboard view) and open Environment Variables from the left menu.
Environment Variables, like any other Workspace Preferences options, can be accessed by the Administrators only.
You can encrypt values so they won’t be presented in plain text.
Now, once saved, you can use them simply by providing $name in Buddy’s actions options.
SSH command box
Currently, Environment Variables are available in every project per workspace. In the next iteration we will provide variables per project only.
Have more questions about Environment variables? We are happy to hear them. Please send us any suggestions how you would like to push it further. Contact Us
Customer Success Manager