Jenkins is an integration tool that allows continuous development, test, and deployment of newly created code. Jenkins can be implemented in-cloud as well as on-premise and Cutover is able to integrate with both setups. Use Cutover to gain visibility across your organization into complex, sequenced Jenkins jobs that can be configured in Cutover with or without parameters, for an easy way to build the process that will seamlessly execute your next application release.  

What can the Jenkins integration do?

Use our integration to connect to Jenkins and trigger ‘jobs’ allowing you to perform work such as building software packages and running tests. Select the associated Jenkins Task Type to configure the Jenkins task. The Task Details panel can be edited to include the Jenkins branch information. 

Jenkins 2

Once the Jenkins task is started within Cutover, the job will start running in Jenkins. Cutover will display a status to show the progress of the integration. These statuses are Connecting, Queued, Build percentage, and Completed. Real-time progress is shared back in Cutover and once the job is finished in Jenkins, the task will be completed automatically in Cutover.

Jenkins 1

Prerequisites

You will need to have a self-hosted Jenkins Server URL and a Jenkins Authentication token. You will also need the email address and username of the user with API access. 

Jenkins

integration FAQs

How do you authenticate? This Cutover service can connect directly to Jenkins. If needed, individual user OAuth tokens can be used. Cutover completely encrypts any authentication tokens that are entered. All data is encrypted at rest and in transit.
How do I know if a Jenkins Job fails? Cutover communicates with the Jenkins server to check whether the job has been queued, the build percentage, or if the job has completed. Cutover then displays the status of the Jenkins integration, letting you know if it has been successful.
How many jobs can you perform with one task? For each Jenkins build, a new task will need to be created. For instance, if you wanted to invoke two different Jenkins builds at different stages within one runbook, you will need to add two different Jenkins tasks.

Still have a question?

Get in touch

Cookie consent

By clicking “Accept”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information.