In today’s ever-evolving technical world, **DevOps** has become a necessity. More organizations are embracing DevOps methodologies to take advantage of faster application delivery, enhanced innovation, stable operating environments, and performance-focused employee teams!

There are multiple trends and technologies contributing to the rise of DevOps. **Microservices, containers, and continuous everything** mean more frequent deployments to production. The only way to manage this without overworking is by automating the processes.

What empowers this automation is the massive progress/interests/awareness/investment in CI/CD tools. This, in theory, means that CI/CD platform tools need more love to succeed in this journey.

**Jenkins** is one such tool which is helping us achieve this goal. But unfortunately we don't have a better process or tools to manage Jenkins especially across the companies/organizations.

Why is it so hard to maintain or manage a Jenkins installation?

* Upgrading and maintaining Jenkins could be a tedious process.
* No change versioning, changes through Jenkins UI yields no record of what, when, why and by whom.
* Disaster Recovery could be nerve-wracking.
* Small change request could take days or even weeks to implement.
* No way to right away test a configuration.
* and just a lot of toil.

## What we need

* A simple and consistent framework to make **Everything as a Code**, which combines Jenkins and plugin(s) versions, config along with job configuration.
* Platform allows every team to build, test and run their own Jenkins seamlessly.
* Autonomy to manage it.

In this talk we are going to demo **Jervis**, an ecosystem we built at **Cerner** around Jenkins to address the aforementioned struggles. In short, the tool we use for automating builds and deployments has no way to automate its own management and focusses on dealing with this very problem.

## Audience Takeaway

How to best manage Jenkins and the continuous development ecosystem around it and ease the process of managing all configuration related to Jenkins as code to tackle the upgrades and downgrades with fashion.

## Target Audience

Jenkins Administrators, DevOps Engineers, SRE Engineers, Pipeline Developers, Software Engineers, and anyone who deals with building, releasing and deploy code through Jenkins and has felt the CI/CD process needed improvements as well as a certain degree of robustness.