Jenkins logo
CI/CD and GitOps

Jenkins

Long-established, self-hosted automation server. Jenkins is an open-source automation server used for continuous integration and delivery. Pipelines are written as code in a Jenkinsfile, and a large plugin ecosystem connects it to almost any tool. It is self-hosted, so you control where it runs and are responsible for maintaining it.

When it is the right choice

  • You already run Jenkins with many working pipelines
  • You need complete control over the build environment on your own infrastructure
  • You have unusual integrations that only a Jenkins plugin covers
  • For new projects, a CI built into your Git platform usually needs less maintenance

How we use it

  • Move freestyle jobs to Jenkinsfile pipelines stored in Git
  • Run Jenkins agents on Kubernetes so builds get clean, scalable environments
  • Keep Jenkins and plugins patched, backed up and monitored
  • Migrate pipelines to GitHub Actions or GitLab CI step by step when that reduces effort
Works well with

Often used together

DockerKubernetesAnsibleTerraform
Services

Where it fits in our work

CI/CD and GitOpsReleases that are routine, reviewed and easy to roll backLearn more »After launchInfrastructure that keeps getting cheaper, faster and safer after launchLearn more »
From the blog

Related articles

AI · November 2, 2026CI/CD for Models and PromptsEvaluation gates, model registries, canary releases and rollback: applying CI/CD discipline to prompts and models in LLM applications.Devops · June 11, 2026Simpler Infrastructure, Faster Engineering TeamsSimpler infrastructure helps engineering teams move faster, deploy more efficiently, and focus on building products.Devops · July 17, 2025DevOps Interview QuestionsPrepare for your DevOps interview with beginner questions, clear answers, and practical tips on tools, CI/CD, cloud, and more.
Questions

Jenkins: frequently asked

Should we replace Jenkins?

Only if it costs you more than it gives. A well-maintained Jenkins with pipelines as code can work well; the usual problem is plugins that nobody updates.

How do we make Jenkins more secure?

Keep core and plugins updated, remove unused plugins, restrict who can change jobs and run builds on isolated agents, not on the controller.

Running Jenkins, or deciding whether to? Tell us what you have; the first consultation is free.

Let's talk »