The following is an excerpt from an upcoming research report on "Modern Operations" by IT Revolution (publishers of The Phoenix Project, The DevOps Handbook; producers of DevOps Enterprise Summit).
For decades, the traditional IT organizational model has been based on grouping people by job function or similar skill sets.
Rundeck features a variety of plugin points for both enhancing the user experience and extending the functionality of Rundeck. While it is quite easy to create your own plugins, it is always nice to be able to start with ones that others have made.
In this edition of TWL, we are highlighting a classic that was a contributing spark to the creation of the DevOps movement.
If you flash back to 2009, the idea of a Dev leader and an Ops leader co-presenting was an odd one. You would expect them to be at different conferences, speaking on different topics. So not only was the pairing considered unusual, their content was remarkable.
The idea of tight integration between Dev and Ops to safely achieve a rate of change that was more than ten deployments per day? That was unheard of and widely considered unsafe and foolish. But, there was Paul Hammond and John Allspaw explaining how they did it and how well it was working.
A common question that comes up from time-to-time in the many places where the community discusses Rundeck:
“What’s the difference between Rundeck and Jenkins?”
In short, Rundeck is designed for Operations to work directly with existing tools, services, and systems and to allow secure self-service access to automation for every kind of critical business workflow. Jenkins is a continuous integration server designed for the primary purpose of building artifacts.
