Environment Variables & Secrets

There are several variables available for you to use in your build steps. You can use these to display the information within your application to indicate which version of the application it is or which pull request or commit. Probo.CI also displays some of this information on the shell for each build.

In addition to these, any secrets or variables that you define in your project or organization will be included in this as well. Note that if you specify the same secret both in the project and organization, the value from the project will override the organization value.

In PHP, these are available via the getenv() function.

In Dotnet, these values are passed to any web service that you run if applicable or via any other mechanism to read system environment variables.

Adding Your Own Secrets

In addition to the built-in variables above, you can define your own values — API keys, tokens, passwords, or any configuration your build needs — from the Secrets area of the Probo portal at app.probo.ci. Each secret you add is exposed to your build as an environment variable. Because they live in the portal rather than your repository, secrets stay out of your codebase, and their values are masked in the interface (shown as dots, revealed with the eye icon) so they aren’t exposed at a glance.

Secrets can be defined at two levels. When the same key exists in both places, the project value overrides the organization value.

Organization Secrets

Secrets set at the Organization level are available to every project the Organization owns.

1. Sign in to the Probo portal and open your Organization.
2. Select the Secrets tab in the left sidebar.
3. In the Key field, enter the environment variable name (for example, MY_SECRET_KEY).
4. In the Value field, enter the value.
5. Click Add a secret to save it. The value is masked once saved; use the eye icon to reveal it.

Project Secrets

Secrets set on a project apply only to that project and take precedence over Organization secrets that share the same key.

1. From your Organization, open the project you want to configure.
2. Select the Secrets tab in the project’s left sidebar.
3. Enter the Key and Value, then click Add a secret.

Removing a Secret

To delete a secret, click the red X to the right of its entry in the list.

Using Secrets in a Build

Once saved, reference your secrets in .probo.yaml build steps just like the built-in variables above — for example $MY_SECRET_KEY in a shell command, or read them from your application at runtime (getenv('MY_SECRET_KEY') in PHP). The real value is available inside the build container while remaining out of your committed code.

Related Articles & Information

---

Managing Your Secrets