Jenkins vs Kubernetes
Side-by-side trajectory, velocity, and editorial themes.
Jenkins keeps its weekly drumbeat going: bug fixes, dialog refinements, and a quiet UI overhaul.
Jenkins has shipped a release every week for the past six weeks, all in the 2.55x–2.56x band. The bulk of each release is bug fixes plus incremental UI work behind the experimental App Bar and dialog refinements. The most notable functional change was 2.562 dropping jarsigner in favor of relying solely on GPG signatures for war-file integrity.
The project is in steady-maintenance mode with a long-running, low-risk modernization of the admin UI rolling out feature by feature behind the experimental flag. Regressions from prior weeks keep getting cleaned up release-by-release, suggesting the UI rewrite is the main source of churn. No directional roadmap changes are visible in the entries.
Expect the experimental App Bar and refined dialogs to keep expanding to more pages while the weekly bug-fix cadence continues. The jarsigner-to-GPG-only move likely sets up further toolchain cleanup in upcoming releases.
Kubernetes 1.36 leans into AI/ML scheduling and control-plane scaling.
The 1.36 cycle is graduation-heavy, with PSI metrics, declarative validation, and volume group snapshots all promoted to GA. Alongside that, the project is making architectural moves around workload scheduling (a new PodGroup API), API-server safety (Mixed Version Proxy on by default), and very-large-cluster scaling (server-side sharded list and watch in alpha). Etcd 3.7 has hit beta in parallel.
Kubernetes is repositioning the control plane for two pressures at once: AI/ML batch workloads, where gang scheduling and DRA are becoming first-class concerns, and very-large clusters, where the control plane itself needs to shard. The pattern across this cycle is consolidation — old experimental scaffolding is reaching GA or being removed (ExternalIPs), while new APIs land with explicit separation of static template from runtime state. Less feature sprawl, more API hygiene.
Expect 1.37 to push server-side sharded watch toward beta and to keep extending DRA's reach into native resources like memory and networking. Workload-aware scheduling will likely accumulate scheduler-plugin-level coordination patterns next, with downstream batch frameworks starting to converge on the PodGroup shape.
See more alternatives to Jenkins →
See more alternatives to Kubernetes →