Command Execution Functionality Overlap Jenkins

Written by Rajat Bhargava on July 3, 2014

Share This Article

Jenkins is becoming the open source standard for continuous deployment continuous integration (CICD). We use it here at JumpCloud. However, when talking about our command execution functionality within our Identity-as-a-Service platform, we are sometimes asked if we overlap with Jenkins. The simple answer is no, but let’s step back for a second.

Continuous Integration, Continuous Delivery

Jenkins is a great tool for your development team. They can leverage it to build their software, ensure that it passes your automated tests and is ready for deployment. That’s the part of the process that’s continuous integration.

The step where JumpCloud becomes a part of the picture and potentially useful is that next step – pushing to production. Or, rather, the continuous delivery part.

As software applications become more complicated, that last step of pushing to production is also getting more complicated. Your application may need to deploy to numerous servers across your infrastructure which may be in multiple data centers / cloud providers. That’s where JumpCloud comes in. With JumpCloud’s command execution functionality, we enable you to execute tasks across servers in your infrastructure. Those tasks can be chained together. In short, you can take a complicated chain of tasks across any number of servers and automate it.

And, that’s exactly what you want to do in the case of pushing software out to your production environment. Once Jenkins has built the software, an automatic notification can be sent to JumpCloud through a Webhook and that will kick off the process of getting your software deployed.

Although you may be wondering what a Directory-as-a-Service® platform has to do with pushing out tasks to servers? With a cloud-based directory service, you have the ability to centrally execute tasks across your Windows, Linux, and Mac infrastructure. Think of it as GPOs for all of your server platforms. Organizations have leveraged DaaS’ ability to execute tasks for a wide variety of different problems and create policies for those items.

Closing the Loop in Continuous Delivery

Leveraging Jenkins and JumpCloud together completes the process of getting your new functionality out to your users as quickly and automatically as possible. As your organization grows and you want to push new functionality continuously, a leveraged, automated process with both Jenkins and JumpCloud can work for you.

So, if you are leveraging Jenkins and struggling with that next step – how to automate the process of getting your software out to production, give JumpCloud Directory-as-a-Service a try. Automating the execution of your server tasks is a part of the overall functionality of our identity management platform. Or, drop us a note to learn more about our server orchestration tool.

Continue Learning with our Newsletter