Search posts, papers, and topics
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 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 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.
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.
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.
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.
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.
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 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.
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.
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.
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.