Jenkins to Cutover integration

Share this post:

Cutover

May 17, 2021

Jenkins is an automation server, managing software builds and continuous deployments. It is a customer-hosted service that performs Jenkins \"jobs\" to complete actions, which are defined in code. Jenkins can be implemented in-cloud as well as on-prem, and Cutover is able to integrate with both setups. Jenkins is an automation server, managing software builds and continuous deployments. It is a customer-hosted service that performs Jenkins "jobs" to complete actions, which are defined in code. Jenkins can be implemented in-cloud as well as on-prem, and Cutover is able to integrate with both setups.

Skip to technical docs

The challenge

As software release gets increasingly complex, especially post-build, visibility into the Continuous Delivery cycle gets lost due to the multiple systems and stakeholders involved. Usually, only the engineer who configured these tools has full knowledge (and usually access to) the ecosystem. Upstream and downstream systems depend on a well-timed execution cycle for a smooth, timely & seamless release. With Cutover, your DevOps tools can work together, increasing their value by providing the observability & orchestration needed to drive forward your automation goals.

 

How does the Jenkins integration work?

Through Cutover, you can easily initiate pre-defined Jenkins \"jobs\" which allow work to be performed via a Cutover runbook (e.g. build a software package or run test scripts). This means that you don't need to perform tasks in Jenkins directly and you can manage your work in one central place. 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.

Through Cutover, you can easily initiate pre-defined Jenkins "jobs" which allow work to be performed via a Cutover Runbook (e.g. build a software package or run test scripts). This means that you don't need to perform tasks in Jenkins directly and you can manage your work in one central place. 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.

Status in progress:

Build complete:

 

Want to find out more information about our Jenkins integration? Get in touch

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.

Will the Jenkins Integration timeout?
If your Jenkins server is at max capacity, and another job is queued, this could lead to the request timing out.

Can you perform multiple jobs on one task?
There is currently only one Jenkins Job allowed per task.

What do I do if the Jenkins Job fails?
We report the status of the Jenkins integration back into Cutover, so you know if your integration has been successful. Cutover communicates with the Jenkins server, so you know whether the job has been queued, the build percentage, or completed.

Does this integration run in rehearsal?
This integration does not run in rehearsal by default

Can Cutover check the status of a build not started in Cutover?
Cutover can only retrieve information about a job that has been started from Cutover.

What are the states of the Jenkins integration?
A task associated with Jenkins has three states:

      • Connecting
      • Queued
      • Build percentage
      • Completed

 

Tags
Share this post:
Webinar /
You're in the Cloud. Now what?
Webinar /
Solving migration challenges with automation, governance, and controls
Operational resilience /
Can surgical scrutiny save us from Fastly outages?