Private corporate batches, live online cohorts and 1-on-1 mentoring in CloudBees CI on top of Jenkins — operations centre, managed controllers, configuration as code, the Assurance Program and CD/RO — taught by a practitioner who runs it in production.
20 years across DevOps, SRE and Security · 10,000+ engineers trained · Trained teams at JPMorgan Chase, Verizon, Nokia and the World Bank
Principal DevOps Engineer & Architect
Rajesh teaches CloudBees as the enterprise layer above Jenkins rather than as Jenkins again: operations centre and managed controller provisioning on Kubernetes and traditional platforms, Configuration as Code bundles that make a controller reproducible, the Assurance Program and Beekeeper across upgrade and rollback, role-based access and credential scoping for a shared multi-team platform, Pipeline Template Catalogs and Cross Team Collaboration, and migration of an existing open-source Jenkins estate onto managed controllers. Sessions run against a live operations centre, including breaking an upgrade and recovering it.
Twenty years across DevOps, SRE and Security, in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe and others. He has trained engineers at JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus — more than 10,000 people personally. He teaches what he runs, not what he reads.
You are booked with a named engineer, and that is who turns up. Marketplaces and larger providers rotate whoever is free, so the person who sold you the agenda is rarely the person teaching it.
The same trainer is available for the next engagement, which matters when a team builds on what it learned last time.
Your batch is assigned a named trainer before it starts, and that is who teaches it. See the full faculty.
Engagements are matched on the tool, not the calendar. For CloudBees that means a trainer who has run it in production — CloudBees CI on top of Jenkins — operations centre, managed controllers, configuration as code, the Assurance Program and CD/RO — rather than whoever is free that week. You are told who is teaching before you commit, and that person is on the discovery call that shapes the agenda.
Where a batch is large enough to need a second trainer, the pairing is declared up front. The lead trainer stays accountable for the syllabus and the assessment either way.
Principal DevOps Engineer & Architect
Twenty years across DevOps, SRE and Security in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe, IBM/Emptoris, Ness, MindTree and Accenture. He has trained more than 10,000 engineers personally, at organisations including JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus. He teaches what he runs, not what he reads.
Teams of 8–30
Custom agenda, your timezone, onsite or online, NDA-friendly.
Request a quoteIndividual engineers
A private instructor and a curriculum built around your goal.
₹99,999Individuals who want peers
Scheduled batch, max 8 to 10 hours of live instruction.
₹34,999A private batch starts with a discovery call. We look at the stack you actually run — the CI system, the cloud, the constraints — and map the agenda onto it, so examples use your topology rather than a generic one.
Delivery is onsite at your premises, live online, or hybrid, scheduled around your release calendar rather than ours. Batches run 8 to 30 engineers.
Every attendee leaves with recordings, slides, lab repositories and a completion certificate. You receive an attendance and assessment report. Invoicing supports PO and GST.
Talk to us about a private CloudBees batchCloudBees is the commercial platform built on top of Jenkins for organisations that have outgrown a single controller. Open-source Jenkins is one instance, administered by hand, with whatever plugins someone installed. CloudBees CI replaces that with a fleet model: an operations centre that provisions and governs many controllers, a supported plugin baseline that is tested as a set, configuration expressed as code rather than as clicks, and role-based access that spans the whole estate rather than one instance.
The distinctive pieces are worth naming precisely. Managed controllers are provisioned from the operations centre — on Kubernetes for modern cloud platforms, or on traditional VM-based platforms — with shared agents, shared credentials and single sign-on. Configuration as Code bundles describe a controller's entire configuration, including jobs and plugin catalogues, as versioned files, which makes a controller reproducible and a change reviewable. The CloudBees Assurance Program, enforced by Beekeeper, defines verified and compatible plugin tiers and keeps a controller on a known-good set through upgrades. Pipeline Template Catalogs, shared libraries and Cross Team Collaboration let a platform team publish golden pipelines instead of copying Jenkinsfiles. Pipeline Explorer makes failures in very large pipelines findable.
CloudBees also sells beyond CI. CloudBees CD/RO, which came from Electric Cloud, handles release orchestration and deployment across environments and approval gates. Feature management provides flag-based rollout. For a platform team the practical question is not whether CloudBees is better than Jenkins — it is the same engine — but whether the fleet governance, supported plugin baseline and configuration-as-code model are worth the licence against the cost of building and maintaining those capabilities yourself.
Large enterprises rarely have one Jenkins. They have thirty, grown per team, each with its own plugin set, its own security model and nobody who can say what would happen if one were rebuilt. That sprawl is the specific problem CloudBees CI is bought to solve, and the organisations that buy it need engineers who can operate a controller fleet rather than a single server.
The skills gap is sharply defined. Plenty of people can write a Jenkinsfile. Far fewer can provision a managed controller from an operations centre, express a controller entirely as a Configuration as Code bundle, run an upgrade through Beekeeper without a plugin conflict taking down a team's builds, design role-based access for forty teams sharing one platform, or migrate a decade-old open-source Jenkins estate onto managed controllers without losing history and credentials.
There is also a cost-justification dimension that keeps showing up in real engagements. Someone has to be able to say what the licence is actually buying, which capabilities a competent team could replicate with open-source Jenkins plus discipline, and where the supported plugin baseline and fleet governance genuinely pay for themselves. That is an engineering judgement, and it needs someone who knows both products properly.
The honest comparison first. Where a single open-source controller stops scaling, what controller sprawl actually costs, and the specific capabilities CloudBees adds — fleet provisioning, supported plugin baseline, configuration as code, estate-wide access control and support. Including where open-source Jenkins plus discipline is the better answer.
Topics: The failure modes of a grown Jenkins estate · CloudBees CI editions and what each includes · Capability-by-capability comparison with open-source Jenkins · Licensing model and how cost scales with the fleet · CloudBees CI, CD/RO and feature management — the product boundaries · Where CloudBees is not worth it · Support model and the CloudBees knowledge base
How the fleet fits together. The operations centre as the control plane, managed and client controllers, shared agents and shared clouds, credential and security propagation, and the difference between a Kubernetes-based modern cloud platform and a traditional VM-based one.
Topics: Operations centre responsibilities and what it does not do · Managed controllers versus client controllers · Modern cloud platforms on Kubernetes versus traditional platforms · Shared agents, shared clouds and agent allocation · Credential propagation from operations centre to controllers · Single sign-on and identity across the fleet · Licensing enforcement and connectivity requirements · Sizing controllers and planning fleet capacity
Standing the platform up. Helm-based installation on Kubernetes, ingress and TLS, persistent storage for controllers, resource requests and limits, then the traditional platform path for estates that are not on Kubernetes — and the day-one configuration both need.
Topics: Helm installation on Kubernetes and values that matter · Ingress, TLS and hostname strategy · Persistent volumes, storage classes and controller data · Resource requests, limits and controller sizing · Installing on traditional VM-based platforms · Provisioning the first managed controller · Agent clouds: Kubernetes agents, static agents and pod templates · Networking, proxies and air-gapped installations
The capability that makes a controller reproducible. CasC bundles for the operations centre and for controllers, what belongs in jenkins.yaml, items.yaml and plugins.yaml, variable substitution, bundle validation, and promoting a bundle through environments in source control.
Topics: CasC bundle structure: bundle.yaml, jenkins.yaml, plugins.yaml, items.yaml, rbac.yaml · Exporting configuration from an existing controller · Jobs and folders as code with items.yaml · Variables, secrets and environment-specific substitution · Bundle validation and dry-run before apply · Bundle versioning, distribution and hot reload · Controller templates for repeatable provisioning · What CasC still cannot express, and how to handle the remainder
Plugin governance as an enforced system rather than a policy document. Verified and compatible tiers, Beekeeper enforcement and warnings, plugin catalogues for anything outside the baseline, and the upgrade procedure — including rollback when a plugin conflict surfaces after the restart.
Topics: The CloudBees Assurance Program and its plugin tiers · Beekeeper: enforcement, warnings and remediation · Plugin catalogues for non-baseline plugins · Pinning, exceptions and the risk they carry · Controller upgrade procedure and pre-flight checks · Rollback and recovery from a failed upgrade · Auditing an inherited plugin estate against the baseline · Coordinating upgrades across a fleet without stopping every team
Sharing one platform between teams that must not see each other's credentials. Role-based access defined at operations centre level and inherited down, folder-scoped roles, credential scoping, single sign-on and group mapping, and the controlled-agent and script-approval questions that arise when Jenkins executes arbitrary code.
Topics: Role-based access control across the operations centre and controllers · Roles, groups and inheritance through folders · Folders Plus and scoped credential domains · Single sign-on: SAML, OIDC and LDAP group mapping · Credential scoping and preventing cross-team access · Controlled agents and restricting where builds run · Script security, sandboxing and approval workflow · Audit trail and evidence for compliance review
Stopping every team from writing the same Jenkinsfile. Pipeline Template Catalogs for governed, parameterised pipelines, shared libraries and their versioning, Cross Team Collaboration for event-driven pipeline triggering, and Pipeline Explorer for finding a failure inside a very large build log.
Topics: Pipeline Template Catalogs: authoring, publishing and consuming · Governed templates versus freely editable Jenkinsfiles · Shared libraries, versioning and testing library code · Cross Team Collaboration: publish and subscribe events between pipelines · Pipeline Explorer for large and long-running pipelines · Workspace caching and build performance · Standardising quality and security gates across teams · Rolling out a template change across consuming teams
Keeping the platform available and moving an existing estate onto it. High availability and horizontal scaling of controllers, backup and restore of controllers and the operations centre, monitoring and analytics, then the migration path from open-source Jenkins including jobs, history, credentials and plugins.
Topics: High availability and horizontal scaling for controllers · CloudBees Backup plugin: scope, schedule and retention · Restore drills for a controller and for the operations centre · Monitoring controllers, agents and build queues · CloudBees analytics and build reporting · Migrating an open-source controller to a managed controller · Handling jobs, build history, credentials and plugin gaps during migration · Decommissioning legacy controllers safely
Beyond continuous integration. CloudBees CD/RO for release orchestration — pipelines spanning environments, approval gates, deployment automation and release visibility — and feature flag management for decoupling deployment from release.
Topics: CD/RO concepts: applications, environments, processes and pipelines · Release orchestration versus pipeline-only CD · Approval gates, manual tasks and compliance evidence · Environment modelling and deployment automation · Release dashboards and portfolio visibility · Integrating CD/RO with CloudBees CI pipelines · Feature flags and progressive rollout · Deciding between CD/RO, Argo CD, Spinnaker and pipeline-native deployment
We rebuild the agenda around the tools you actually run.
Request a custom agendaInstall an operations centre on Kubernetes, provision two managed controllers with shared agents and single sign-on, and prove credential propagation works.
Export a hand-configured controller to a Configuration as Code bundle, destroy the controller, and rebuild it identically from the versioned bundle alone.
Audit a controller against the Assurance Program, add a non-baseline plugin through a catalogue, perform an upgrade that fails, and recover the controller.
Configure operations-centre roles, folder scoping and credential domains so three teams share a controller with no cross-team credential visibility, then verify effective permissions.
Publish a Pipeline Template Catalog with enforced quality gates, consume it from two controllers, then roll out a template change to both.
Migrate a populated open-source Jenkins instance onto a managed controller with jobs, credentials and build history intact, then prove continuity with a restore drill.
Billed yearly at ₹9,996
Max 8 to 10 hours of live instruction
Full program, private instructor
8–30 engineers · custom agenda · onsite or online · PO and GST invoicing
Refunds. If we cancel or postpone a cohort, you get a full refund within 15 days. There is no money-back guarantee otherwise.
Terms. Course material remains licensed to the attendee. Read the terms.
Your data. We don't share it with third parties. Privacy policy.
Certificate of completion
Great learning experience from a very knowledgeable instructor with well-prepared course notes. The lab exercises on AWS instance work well to learn the hands-on side of the course.
Rajesh is a very good trainer I have experienced in DevSecOps training. The number of contents in different topics he has posted on the DevOpsSchool public website are amazing and user friendly for beginners and experienced professionals.
The trainer (Rajesh) provided very good sessions on SRE profession. Not only hands-on learning on the tools but also SRE mindset.
Very good training session. Well explained from the basics to the complex concepts. Also tried to cover practicals and demos within the 3 hour sessions. The learning content and videos are of a great deal of help.
Basics explanation was exemplary from Rajesh where he dealt with complicated topics to be simple. Great learning stuff personally for me.
Very detailed explanation and has lots of patience in attending the questionnaire. Thanks again for your wonderful sessions.
| What matters | YouTube + blogs | Generic online course | Freelance marketplace | DevOpsSchool |
|---|---|---|---|---|
| Named practitioner | No | Rarely | Varies per booking | Yes — same trainer each time |
| Production experience | Unknown | Unknown | Unverified | 20 years, named employers |
| Custom agenda | No | No | Sometimes | Built from your stack |
| Onsite delivery | No | No | Sometimes | Yes |
| Lab environment | None | Sandbox that expires | Varies | Your own cloud — skill goes with you |
| Assessment | None | Quiz | Rarely | Assignments + capstone per module |
| Per-attendee certificates | No | Sometimes | Rarely | Yes |
| Corporate invoicing | No | Limited | Varies | PO and GST |
| Post-training support | None | Forum, time-limited | None | Lifetime forum access |
Tell us the team, the stack and the timeline. You'll get a straight answer, not a sales sequence.
Talk to an advisorPrefer to call or email?
More ways to reach us on the contact page.