2025 Year in Review
CloudBees’ 2025 Year in Review announces its new Unify platform, an AI‑enhanced control layer that sits on top of existing CI/CD tools, and highlights awards and survey results.
Search posts, papers, and topics
63 posts · blog.codeship.com
CloudBees’ 2025 Year in Review announces its new Unify platform, an AI‑enhanced control layer that sits on top of existing CI/CD tools, and highlights awards and survey results.
CloudBees Unify was announced as the Gold winner in the DevSecOps category of the 2026 Cybersecurity Excellence Awards. The post positions Unify as a control‑plane that centralises policy and AI‑aware guardrails, but provides no technical details, code, or measured results.
CloudBees runs a volunteer program called BeeGiving, giving each employee two paid days a year to volunteer. The article describes a bike‑building activity at the company’s sales kickoff, tying community service to culture and employee engagement.
Step‑by‑step tutorial for obtaining a Let’s Encrypt wildcard certificate via DNS‑01 challenge and wiring it into an NGINX server block on Ubuntu 16.04.
The DevOps Agent Kit is an Apache‑2.0 open‑source starter kit that lets you plug an LLM‑based coding assistant into your existing CI/CD, security, and feature‑flag tooling via CloudBees Unify. It ships with seven read‑only example skills, enforces RBAC and audit trails, and normalises data from up to 63 tools so the agent can answer a single “are we good to ship?” question with verifiable evidenc…
The post explains the motivation behind Jenkins' Credentials API, recounts early design mistakes (duplicated username/password types, over‑reliance on the type system), introduces the “Oracles of Identity” concept, and shows how credential domains let users declaratively bind credentials to the right services.
Jenkins Configuration as Code (JCasC) lets you define the Jenkins controller via declarative YAML that mirrors the UI model. The plugin can generate exhaustive documentation and a JSON schema for the YAML, enabling IDE assistance. It also offers a REST API to dry‑run configs before applying them. The post links to related series entries and community resources.
Kohsuke Kawaguchi outlines a few low‑effort ways to keep a Jenkins instance healthy: use jconsole to watch old‑gen heap usage, the Monitoring plugin (or Nagios) to record HTTP latency and queue length, inspect thread dumps for slow pages, and review the built‑in load chart to spot agent under‑/over‑utilisation.
The post describes a proof‑of‑concept DR setup for CloudBees CI on EKS using Velero with custom patches for cross‑region EBS snapshot replication, achieving 15‑minute RPO and sub‑hour RTO. It also outlines the required backup of $JENKINS_HOME, metadata, DNS switch, and the experimental nature of the patches.
GNU Make scans every built‑in implicit rule for each target, adding unnecessary overhead. Using the -r (or --no-builtin-rules) flag disables this scanning and can speed up large or no‑op builds by up to ~30%.
CEO Moritz Plassnig’s note is a high‑level, marketing‑focused announcement about CloudBees’ vision for AI‑augmented software delivery. It contains no technical details, code, or concrete product changes—just broad statements about flexibility, governance, and future “industrialization” of development.
CloudBees Smart Tests adds a “High‑failure‑rate tests” dashboard and a “Quarantine” mode that lets flaky tests keep running but no longer block the pipeline, with manual or automatic thresholds and automatic recovery when failure rates drop.
CloudBees announced a rebrand, including a new logo, typeface, and color palette, to reflect its evolution from an Enterprise Jenkins provider to a strategic cloud transformation partner. The rebrand aims to align with their updated vision, mission, and values, emphasizing flexibility and a "bees-eye view" of software development.
The article is a vendor‑authored marketing piece that lists criteria for picking a GitLab alternative and then promotes CloudBees Unify as a cross‑tool governance layer, with brief mentions of other tools (GitHub, Jenkins, Azure DevOps, Harness, CircleCI). It contains a few quoted survey percentages but no technical deep‑dive, code, architecture diagrams, or independent evaluation.
The article argues that Harness’s “free migration” offer hides significant downstream costs (training, pipeline rebuilds, compliance recertification) and that even after migration you still lack unified governance across heterogeneous CI/CD tools. CloudBees positions its Unify control plane as a tool‑agnostic layer that adds visibility, continuous governance, AI‑driven test selection, and hybrid…
The article compares several test‑intelligence products, highlighting CloudBees Smart Tests as a CI‑agnostic solution that allegedly saved a company 40 K testing hours and doubled release velocity. It also outlines the trade‑offs of coverage‑based, ML‑driven, and flaky‑test‑focused tools.
CloudBees’ CARE Score is a proprietary 0‑100 rubric across six AI‑governance dimensions (cost visibility, budget predictability, productivity measurement, governance maturity, pipeline visibility, token governance). The post shows a gap between leaders’ self‑rated confidence (≈86‑92%) and operational reality (e.g., only ~30% can attribute AI spend to outcomes, ~27% enforce token limits). It offer…
Enterprise AI code generation is outpacing governance: 92% of leaders feel confident but 81% see more production issues; post‑generation stages (review, testing, deployment) are now the bottleneck. Successful adoption requires up‑skilling, end‑to‑end metrics, and tooling (e.g., CloudBees DevOps Agent Kit, PR‑auto‑approval agents).
Autonomous AI agents like OpenClaw are shifting software development from AI-assisted to AI-executed, capable of committing code and orchestrating deployments without human approval. This necessitates robust governance to manage increased risks in security, compliance, and accountability, as traditional DevOps assumptions no longer hold.
CloudBees announces its Unify platform extensions, including a GitHub Actions integration and an MCP Server that adds AI‑aware context to pipelines. The post is a marketing overview with upcoming events and UI change notices.
A report highlights a significant gap between enterprise confidence in AI-generated code and operational reality, with 81% of leaders reporting increased production issues despite high readiness scores. This "code abundance" means code is generated faster than organizations can effectively test, govern, and manage it, leading to challenges in cost attribution and governance.
The post announces CloudBees CI’s new High Availability mode, which splits a Jenkins controller into multiple replicas that are load‑balanced and synchronized via Hazelcast. It claims automatic scaling, fault tolerance, and seamless rolling restarts, but provides no implementation details, metrics, or code.
The article is a marketing overview of CloudBees' agentic AI push, highlighting a webinar, the “Three H’s” governance framework, and the new MCP Server AI integration now on AWS Marketplace. It contains no technical deep‑dive or implementation specifics for engineers.
CloudBees announced Unify, a marketed unified DevOps platform that adds AI‑driven test selection, GitHub Actions integration, and continuous security scanning, promising faster, more secure software delivery for enterprises.
CloudBees announced Philippe Van Hove as its new Chief Revenue Officer. He brings 25 years of SaaS go‑to‑market experience and will lead scaling of the AI‑forward CloudBees Unify solution.
CloudBees announced it was named to Inc.’s 2025 Best Workplaces list, framing the award as validation of its internal culture and values.
This tutorial demonstrates how to set up a Node.js application with a PostgreSQL database using Docker Compose for local development. It covers creating a Dockerfile for the Node.js app and defining both services in a docker-compose.yml file, including volume mounts and environment variables.
This tutorial demonstrates how to set up a PHP/Laravel/PostgreSQL development environment using Docker and Docker Compose. It covers creating a Dockerfile for the PHP application and defining services for NGINX, the PHP app, and PostgreSQL in a docker-compose.yml file.
This article explains what Git merge conflicts are, why they occur when merging different changes to the same file locations, and how they manifest differently in standard merges versus rebases. It provides a strategy for resolving rebase conflicts in feature branches before merging them into a main branch.
This article argues that CMMI (Capability Maturity Model Integration) is an outdated and ineffective methodology for software development. It contends that CMMI's focus on institutionalized process devalues individual talent, stifles innovation, and has failed to prove its worth in the broader technology space.