---
title: "Jenkins | Skills We Assign For | Azendo"
description: "Jenkins on an inherited installation — plugin risk, pipeline-as-code and migration, and the Azendo roles assigned for CI work."
url: "https://azendo.co/skills/jenkins/"
---

[Skills](https://azendo.co/skills/) CI and delivery 

# Jenkins.

Jenkins is a long-established, self-hosted automation server used for builds and deployments. Most Jenkins work today is maintaining or migrating an installation that has been running for years and accumulated plugins, credentials and jobs nobody fully understands.

## Where Jenkins fits on a long engagement.

An old Jenkins is frequently the least-documented critical system an organisation owns. Jobs configured through the UI, plugins pinned to versions that block upgrades, and credentials whose owner left. It works, everyone is slightly afraid of it, and nobody wants to be the person who touches it.

The realistic path is to reduce risk before deciding on a destination: get jobs into version-controlled pipeline definitions, establish which plugins are load-bearing, and prove the server can be rebuilt. After that a migration is a choice rather than a leap.

## What an assigned team does with Jenkins.

An inherited Jenkins is the clearest argument for continuity anywhere in a stack. Its value is entirely in knowing which plugins are load-bearing and which job nobody dares disable, and that knowledge exists in one person or in nobody.

The sensible sequence is risk reduction before migration: jobs into version control, configuration proven reproducible, then a decision. All of it sits under [DevOps managed services](https://azendo.co/services/cloud-and-devops/) with the same specialist across the whole arc.

## What we use Jenkins for.

* Getting jobs out of the UI Pipeline definitions in the repository, so the build is reviewable and recoverable.
* Proving the server can be rebuilt Configuration captured and tested, so the installation stops being a single point of failure.
* Migrating deliberately Moving to a managed runner with a plan and a rollback, rather than a big-bang cutover.

## How Jenkins capacity is assigned.

Legacy pipeline work is assigned under DevOps managed services, and it is the kind of work where continuity matters most, because the value is in knowing the estate. What that figure covers is set out in [how the monthly fee is built](https://azendo.co/pricing/).

## Roles we assign Jenkins for

* [DevOps Engineer Cloud and DevOps](https://azendo.co/services/cloud-and-devops/devops-engineer/)
* [Test Automation Engineer QA and test automation](https://azendo.co/services/qa-engineering-and-test-automation/test-automation-engineer/)

## Service lines it sits in

* [Cloud and DevOps](https://azendo.co/services/cloud-and-devops/)
* [QA and test automation](https://azendo.co/services/qa-engineering-and-test-automation/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in ci and delivery

* [TestFlight — skill we assign for](https://azendo.co/skills/testflight/)
* [App Store Connect — skill we assign for](https://azendo.co/skills/app-store-connect/)
* [Play Console — skill we assign for](https://azendo.co/skills/play-console/)
* [CodePush — skill we assign for](https://azendo.co/skills/codepush/)
* [Bitbucket Pipelines — skill we assign for](https://azendo.co/skills/bitbucket-pipelines/)
* [ArgoCD — skill we assign for](https://azendo.co/skills/argocd/)
* [GitOps — skill we assign for](https://azendo.co/skills/gitops/)
* [CircleCI — skill we assign for](https://azendo.co/skills/circleci/)

## Tell us what your roadmap needs Jenkins for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)