Adding Credentials to Jenkins

Jenkins is famous CI/CD tool, which is open source and allow building applications developed with almost any programing language. It has greater integration capabilities with different tools from other providers and for that setting up credentials is required. Let’s look at how to setup credentials, isolating with a credential domain in Jenkins.
If you have not already installed Credential plugin, install it to Jenkins. Additionally you can install Credential Binding plugin (this plugin let you configure build jobs to inject credentials as environment variables) and Plain Credential plugin (dependency of Credential Binding plugin).

You can go to Jenkins and Click on Credentials in the left menu. Then in credential “Stores scoped to Jenkins” click on Jenkins drop down menu, and click Add domain to define a credential domain.

Define a credential domain, let’s  say we are going to integrate with Jenkins with VSTS, you can define a credential domain for that purpose. You can define specifications to identify the requests for credentials, to verify validity of them to the defined credential domain. But it is not mandatory to specify the specification. Just a name for Credential domain is sufficient.

Once a a credential domain is created you can use Add Credentials menu item inside the credential domain page, as shown in above figure, or use the Add Credential in the drop down menu of the Credential Domain list in the Credentials grid.

You can sect the kind of credential you are adding. Default is username and password.

Scope of the credential can be defined as global allowing it to be used in jobs etc. If a credential is defined in System scope it can only be used in Jenkins server instance integration with other services.

Once saved the credential is available for you to used in the defined scope.