One of the possibilities of the CI server is the ability to talk to third-party services that usually rely on some sort of credentials (such as access tokens or similar) to authenticate the user. Exposing these secrets would be discouraged as they could potentially cause major harm to our company.
Jenkins handles this in a very simple way: it provides a way to store credentials in a safe way that can be injected into the build as environment variables so that we can work with them.
Let's look at some examples. First, we need to create the secrets in Jenkins. In order to do that, we have to go to Manage Jenkins from the home page.
Once we are there, you should see a screen very similar to this one:
We are using the Global ...
