CJE study guide
CJE · Work through your exam, one topic at a time.
The Certified Jenkins Engineer credential is a vendor-style certification aimed at people who build, operate, and maintain Jenkins as a shared automation service rather than just clicking through a single freestyle job. It suits build and release engineers, DevOps practitioners, SREs, and platform teams who own controller and agent infrastructure, write Jenkinsfiles, and get paged when builds queue up or pipelines fail. The CJE study guide has 8 sections and about 3,514 words.
01Jenkins Installation, Configuration, and Administration
This domain tests whether you can stand up a Jenkins controller from scratch, choose the right distribution, wire it to a persistent home directory, and administer it day to day without corrupting state. Expect questions on the WAR file versus native packages, JENKINS HOME layout, JVM and system properties, the setup wizard, and Configuration as Code.
432 words, about 2 min02User Management, Security, and Access Control
CJE questions here separate two ideas beginners merge: authentication (the security realm that decides who you are) and authorization (the strategy that decides what you may do). You also need the credentials model, CSRF protection, and the controller/agent trust boundary.
426 words, about 2 min03Job Types and Build Configuration
Expect questions that ask you to pick the right job type for a requirement and to predict what a given configuration does - retention, parameters, concurrency, and environment variables. Freestyle is the classic form-based job: SCM, triggers, build environment, build steps, post-build actions.
468 words, about 2 min04Pipelines and Pipeline as Code
The heaviest domain by question weight. You must read and write both syntaxes, know the declarative directive set, and understand shared libraries, sandboxing, and durability.
453 words, about 2 min05Source Code Management, Webhooks, and Triggers
Questions test whether a repository change actually reaches a build. You need Git plugin behaviours, the webhook endpoint per provider, and cron semantics for polling and scheduled triggers.
430 words, about 2 min06Build Agents, Distributed Builds, and Cloud Agents
Scheduling, connectivity, and cleanliness. Expect questions on labels, launch methods, cloud provisioning, and what happens to a workspace when an agent is ephemeral.
431 words, about 2 min07Artifacts, Testing, and Plugin Ecosystem
What a build leaves behind, how test results change build status, and how to keep a plugin set healthy. Questions are practical: which step, which path, which status.
421 words, about 2 min08Troubleshooting, Monitoring, and Maintenance
Diagnosis under pressure: reading logs and thread dumps, exposing metrics, and keeping a controller alive across upgrades. Questions often ask for the first thing you check.
453 words, about 2 min