Skip to main content

Dev Station Technology

DevOps

Jenkins services beside our CI/CD builds

We have no published Jenkins build. We have shipped Azure DevOps pipelines and daily CI/CD deployments, and we help teams whose Jenkins controller still runs on Java 17.

0Published builds on Jenkins
21 and 25Java versions Jenkins supports
Sep 2027Planned end of support for Java 21 on Jenkins
2.541.3Final Jenkins LTS that runs on Java 17
What we build

What we would take on with Jenkins

Pipelines

Build, test and deploy steps kept in code.

Java 17 to 21 or 25

Controllers moved before they stop running.

Container builds

Docker multi-stage builds inside the pipeline.

Daily deployments

The rhythm of our crypto platform build, on a Kanban workflow.

Architecture

Where Jenkins would sit

A Jenkins pipeline in the slot Azure DevOps fills
Code
RepositorySource of truth
CI/CD
Jenkins logo
JenkinsWhere it would sit
Azure DevOpsHydrajaws, Verify Auto
Targets
Azure logo
AzureCloud infrastructure
AWS logo
AWSCrypto platform

Illustration. A dashed outline marks where the technology would sit. We have no published build on it.

Versions

Which Java Jenkins needs

If you install an unsupported Java version, the Jenkins controller does not run.

Java requirements on Jenkins, 2022 to 2030
Supported by Jenkins

Source: Jenkins documentation, Java support policy, checked 4 November 2026. Start months are the first weekly release that required each version.

Builds

The closest builds we can show you

Hydrajaws safety testing app built by Dev Station
Construction safety testing, United Kingdom

Hydrajaws Limited

Azure DevOps pipelines and rebuilt environments after the previous owner left no documentation.

500%Surge in potential clients
Cryptocurrency marketing platform built by Dev Station
Fintech, Hong Kong

Cryptocurrency marketing platform

Kanban workflow with daily CI/CD deployments for rapid iteration and client feedback.

30,000+Concurrent users the platform had to support
Fit check

When Jenkins is the right call

Pick Jenkins when

  • You already run Jenkins and need it kept healthy
  • Your builds need plugins that only Jenkins has
  • You want pipelines on your own servers

Look elsewhere when

  • You need a published Jenkins build to inspect, which we do not have
  • A new project on Azure, where we ran Azure DevOps
  • Nobody on your team will maintain a controller
Stack

What Jenkins usually sits beside

Docker logoDocker
Kubernetes logoKubernetes
Azure logoAzure
AWS logoAWS
Terraform logoTerraform
Java logoJava
FAQs

What buyers ask first

Which Java version does Jenkins need?

Java 21 or Java 25. Java 17 is unsupported, and its final LTS was 2.541.3 in March 2026.

Do you have a published Jenkins build?

No. We say so on the first call and show the nearest work, which is Azure DevOps pipelines and daily CI/CD deployments.

Does my build JDK have to match the controller?

No. The JDK that builds your projects does not have to match the one running Jenkins, though some plugins set stricter rules.

Who owns the code and the cloud accounts?

You do, from the first commit. Repositories and cloud accounts stay in your name.

Tell us which Java your Jenkins runs on

Thirty minutes on your controller, your plugins and your pipelines. No sales pitch.

Let's Talk