Search posts, papers, and topics
63 posts · blog.codeship.com
Agentic coding lets AI agents write, test, and submit code autonomously, shifting the bottleneck from writing to governing code in production. Enterprises face rising failures, unclear ownership, growing costs, and weakened controls, which require a unified pipeline visibility layer.
A product‑focused overview of CloudBees CD/RO’s new integration with Argo Rollouts, describing the supported blue‑green and canary strategies, service‑mesh compatibility, and UI/analytics features. No deep technical walkthrough or performance data.
A CloudBees blog post argues that existing CI, security, and QA tools don’t give release managers a complete view of AI‑generated code risk. It claims tool consolidation rarely helps and proposes a “control plane” (CloudBees Unify) that aggregates signals from multiple tools and adds AI‑driven test prioritization. The piece is largely promotional, with no concrete implementation details, metrics,…
AI‑generated code breaks the traditional chain of ownership: developers merge PRs they didn’t write, reviewers approve logic they didn’t originate, and QA validates tests chosen by a model. A CloudBees survey shows 81% of firms see more production failures from AI code, and accountability often drifts upward to CTO/VP. The post argues role‑based accountability isn’t enough; you need end‑to‑end tr…
The article explains what Jenkins is—a free, open‑source CI/CD automation server that runs pipelines defined as code and can be extended via thousands of plugins. It also outlines Jenkins’ strengths, drawbacks, and how CloudBees adds enterprise‑grade security and scaling features.
The article warns that unchecked CI/CD sprawl— orphaned pipelines, hard‑coded secrets, and permissive runners— creates a hidden attack surface, and that AI‑driven agents will amplify the problem. It recommends a governance layer with real‑time inventory, policy‑as‑code, and AI guardrails to bring the software factory under the same security rigor as production.
This article argues that independent microservice deployments, while seemingly fast, often lead to complex and fragile releases due to environment drift and implicit dependencies. It advocates for "application-level releasing," where a consistent, validated snapshot of interdependent components is promoted together across environments to restore predictability and stability.
Use Git's `includeIf` conditional includes to automatically load per‑directory `.gitconfig` files, letting you set different `user.email` and `signingkey` values for Apache, work, and personal repos without manual `git config` calls.
The post introduces CloudBees Unify, a layer that plugs into existing Jenkins controllers to give a unified CI dashboard, security scanning, and artifact traceability without changing pipelines. It outlines a phased rollout—from a 30‑minute quick start to multi‑week scaling—aimed at large orgs seeking enterprise‑scale visibility.
CloudBees Unify is a control‑plane layer that aggregates data from existing CI/CD, security, and release tools to give a single delivery record. It claims to improve test efficiency (98 → 30 min) and enforce governance policies across pipelines, with an AI assistant for incident triage. The post is a product‑focused webinar recap with limited technical depth.
The article walks through configuring Jenkins to launch EC2 instances as build agents on demand, covering AWS IAM setup, security groups, key pairs, AMI selection, and the Jenkins EC2 plugin configuration. It shows how idle termination can keep costs low while providing elastic build capacity.
Jenkins now supports a build‑branch strategy to skip the initial build that runs when a multibranch job first indexes its branches. Install branch‑api 2.3.0+ and basic‑branch‑build‑strategies 1.3.0+, then enable **Skip initial build on first branch indexing** in the job’s Build strategies UI. The strategy works by overriding `BranchBuildStrategy.isAutomaticBuild` in the plugin code.
A four‑stage model for adopting agentic AI in software delivery pipelines, warning that Stage 3 (bounded autonomous execution) is arriving faster than governance programs. The post explains the stages, required controls (scoped credentials, fail‑closed defaults, tamper‑evident logs), and uses the OpenClaw incident as a cautionary example.
FileInputStream and FileOutputStream implement finalize, which forces objects onto the finalizer queue and can cause long GC pauses in programs that open many files. Switching to Files.newInputStream and Files.newOutputStream (Java 7+) eliminates the finalizer overhead and improves I/O‑heavy workloads.
The article defines DevOps as a culture that aligns people, processes, and tools around rapid, reliable software delivery, and cites high‑profile companies that claim faster releases and happier engineers after adopting it.
CloudBees announced AI First Responder (AIFR), an AI‑powered incident‑triage assistant that lives in Slack and leverages the CloudBees Unify control plane and its knowledge graph. AIFR claims to summarize logs, suggest root causes, and optionally trigger GitOps remediation, all while logging actions for governance. The feature is in limited preview and available to a design‑partner program.
The article argues that enterprises need a DevSecOps control plane to unify fragmented CI/CD tools, enforce security policies, and provide AI‑aware context. CloudBees Unify is presented as a solution that claims large reductions in release prep time and outages without requiring tool migration.
Flaky tests silently erode CI reliability, waste compute and developer time, and let real bugs slip into production. The post quantifies the cost (≈2.5 % of developer time, $5.67 per manual investigation vs $0.02 for auto‑rerun) and critiques common band‑aid approaches (retries, quarantine, manual triage). It argues that visibility—detecting flaky tests, predictive test selection, and automated t…
Jenkins' JSON API can return huge payloads; the depth parameter limits nesting but still may be large. The tree query parameter lets you explicitly request only the fields you need, cutting response size dramatically.
A step‑by‑step tutorial showing how to convert Yocto BitBake buildstats into ElectricInsight annotation files (using the bb2anno utility) and then visualize build timelines, parallelism, and task‑type heat maps to spot bottlenecks.
A practical walkthrough of Jenkins shared libraries: repository layout, global vs scoped loading, a simple Groovy var (gbuild) that wraps Gradle, and the steps to configure and use the library in a pipeline.
The post announces CloudBees CD/RO’s integration with Argo Rollouts, describing the tool’s blue‑green and canary strategies, service‑mesh support, and UI/analytics benefits, but offers no deep technical guidance.
The Jenkins Templates plugin (CloudBees) lets admins define reusable builder and job templates, propagating changes to all jobs and hiding complex configuration from end users.
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.
The article defines continuous security as an AI‑augmented, unified control plane that embeds security checks into CI/CD pipelines, contrasting it with fragmented tool sprawl that creates alert fatigue. It promotes CloudBees Unify as a solution that deduplicates findings, enforces policy‑as‑code, and automates audit evidence.
This blog walks through the open‑source DevOps Agent Kit, which lets Claude Code or Cursor act as a DevOps assistant by connecting to CloudBees Unify, Jira, and Slack via MCP servers and to GitHub via the CLI. It provides a repeatable setup (Docker, Node, env file) and seven slash commands for pipeline overview, triage, security, release readiness, flag management, CI health scoring, and Jira tic…
A marketing announcement for CloudBees' new Private SaaS Edition, a managed Jenkins‑as‑a‑Service offering that runs on private or virtual private clouds using Docker, Mesos, OpenStack or EC2. No technical details, architecture diagrams, or implementation guidance are provided.
ElectricCommander 4.2 adds a redesigned Resources UI, bulk agent install/upgrade, optional trusted SSL connections, zone‑based segmentation with gateways, new API commands, JSON transport, and a bundled standard license. The release is a typical product update with no deep technical analysis.
The copyartifact plugin now supports Jenkins Pipeline via a core step (v1.34). Use the generic `step([$class: 'CopyArtifact', …])` syntax to pull artifacts from another job, with all existing options available through the Snippet Generator. A native pipeline step is planned.
CloudBees Unify adds an embedded AI assistant that answers questions using pipeline state, policies, and delivery history, aiming to reduce context‑switching and hallucinations. The beta is now available but the post offers only product positioning, not technical details.