Jenkins
Automate your testing workflow directly from Jenkins CI/CD pipelines.
Enterprise feature
External provider integrations are available on Enterprise plans. Contact the nunu team if you are interested.
What do we need?
- Jenkins Base URL: Your Jenkins server URL (e.g., https://jenkins.example.com )
- Project ID: The Jenkins job or project name
- Username: The Jenkins username associated with the token
- Access Token: An API token generated from your Jenkins user settings
Project ID
The Project ID is the same as the Jenkins job name. You can find it in the dashboard or in the project URL (e.g., yourproject in https://jenkins.example.com/job/yourproject/ ).
Steps to locate it:
- Open your Jenkins Dashboard.
- Find the job or project you want to integrate.
- Copy the project name and paste it into the Project ID field in the Deployment Configuration Editor.
Username & Access Token
Jenkins API tokens are user-specific and tied to the account that creates them. A user must generate their own token via their profile.
Steps to generate a token:
- Go to your User Profile (usually top-right corner).
- Navigate to the Security tab.
- Under API Token > Current token(s), click Add new Token.
- Give it a descriptive name (optional), then click Generate.
- Copy the token and paste it into the Access Token field in the Deployment Configuration Editor, along with your username.
You won’t be able to view the token again after closing this dialog. Be sure to store it securely or generate a new one if needed.
Example Config:
Check out Deployment Configuration for more details on how to configure your deployment settings on nexus and integrate with your CI/CD pipeline integration.