Private corporate batches, live online cohorts and 1-on-1 mentoring in continuous integration and delivery pipelines, from freestyle jobs to multibranch pipeline-as-code — 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 Jenkins as both a pipeline tool and a system to be operated — freestyle projects and the full pipeline model including Multibranch and Blue Ocean, agent fleet management across Linux and Windows, security and authorisation, backup, restore and upgrade procedure, plugin governance, and integration with Git, Maven, Gradle, SonarQube, Artifactory, Docker, Terraform and Ansible. Sessions run live against a working controller and agents, including deliberately breaking and restoring an instance.
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 Jenkins that means a trainer who has run it in production — continuous integration and delivery pipelines, from freestyle jobs to multibranch pipeline-as-code — 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 Jenkins batchJenkins is an open-source automation server used to build, test and deploy software. At its simplest it watches a repository, runs a build when something changes, and reports the result. In practice it becomes the place where an organisation's delivery process is encoded — the sequence of compile, test, scan, package, promote and deploy that every change must pass through.
Jenkins is built around a controller and agents. The controller schedules work and holds configuration; agents execute it, which is how builds scale across machines and platforms. Jobs come in two broad shapes: freestyle projects configured through the web interface, and pipelines defined as code in a Jenkinsfile stored beside the application. Pipeline-as-code is the modern default, because it versions the delivery process with the software it delivers, and Multibranch Pipeline extends that to every branch automatically.
What makes Jenkins ubiquitous is also what makes it demanding: the plugin ecosystem. Integration with Git, Maven, Gradle, SonarQube, Artifactory, Docker, Kubernetes, Terraform, Ansible and hundreds of others comes from plugins, and an unmanaged plugin estate becomes a maintenance and security liability. Running Jenkins well is as much about administration — security, authorisation, backup, upgrades, agent management — as about writing pipelines.
Continuous integration is no longer optional, and Jenkins remains the most widely deployed CI system in enterprises, particularly where builds are heterogeneous, on-premises, or bound by constraints that hosted runners cannot satisfy. Even organisations adopting newer tools usually have a substantial Jenkins estate that has to be maintained, secured and often migrated.
The demand splits into two distinct skills. One is pipeline authoring — writing declarative and scripted pipelines that are readable, reusable and testable rather than a thousand lines of shell. The other is administration: securing an instance that can execute arbitrary code, managing an agent fleet, controlling plugin sprawl, and performing upgrades and restores without losing build history. Organisations frequently have people who can do the first and nobody who can do the second.
There is also a migration dimension. Teams moving from freestyle jobs to pipeline-as-code, or consolidating multiple Jenkins instances, need someone who understands both the old shape and the new one well enough to move between them without losing behaviour.
The practice before the tool. What continuous integration actually requires, how delivery and deployment differ from it, and an honest comparison of Jenkins against TeamCity and Bamboo.
Topics: What continuous integration is · Benefits of CI · Continuous delivery vs deployment · CI tooling landscape · Jenkins vs TeamCity vs Bamboo · Where Jenkins is the wrong choice
Getting a controller running across the deployment shapes teams actually use, then the dashboard and the administrative surface underneath it.
Topics: Prerequisites and sizing · Installing via yum and apt · Installing on Windows via MSI · Running under Tomcat · Running as a service · Starting and stopping · Dashboard tour · Manage Jenkins overview
The job type most existing estates are built from. Every tab and what it controls — because migrating away from freestyle requires understanding what it was doing.
Topics: Freestyle general configuration · Source code management · Build triggers · Build environment · Build steps · Post-build actions · Views and build history · Credentials and people
Jobs for the build systems teams actually run — Java with Maven, Ant and Gradle, .NET with MSBuild, and C++ driven by batch — with the environment and tooling configuration each requires.
Topics: Java and Maven builds · Java and Ant builds · Java and Groovy builds · DOTNET and MSBuild · C++ via batch · Tool installations and auto-installers
Scaling beyond the controller. Adding Linux and Windows agents, managing the fleet, labelling and targeting, and thinking about availability.
Topics: Adding a Linux agent · Adding a Windows agent · Agent connection methods · Node management · Labels and targeting · Executor configuration · High availability considerations
When builds run and how they behave. Manual, scheduled and push-triggered builds, parameterisation, concurrency, chaining and throttling.
Topics: Manual builds · Scheduled builds · Script-triggered builds · Triggering on git push · Parameterised jobs · Concurrent builds and executors · Chaining and downstream projects · Throttling builds
The part most teams neglect until an incident. Jenkins executes arbitrary code by design, so authentication, authorisation, credential handling and folder-level access control are load-bearing. Plus backup, restore, upgrade and the command line.
Topics: Security in Jenkins · Authentication · Authorisation strategies · Credential management · Folder and subfolder access · Upgrades · Backup · Restore · Jenkins CLI
The ecosystem that makes Jenkins capable and fragile in equal measure. Installing, configuring and updating plugins, governance practice, and the integrations that matter across source control, build, quality, security and infrastructure tooling.
Topics: Installing and configuring plugins · Updating plugins and version pinning · Plugin governance and risk · Git, Jira and Maven integration · SonarQube, JUnit, JaCoCo and Coverity · Docker and Kubernetes · Ansible, Terraform and Packer · Selenium and Gradle
Making build results legible. Test, coverage, quality and security reporting, and getting feedback to the people who need it through email, Slack and dashboards.
Topics: JUnit reports · SonarQube reports · JaCoCo coverage · Coverity reports · Selenium and Cucumber reports · Build pipeline dashboards · Email and advanced email notification · Slack notification
The modern shape of Jenkins. Declarative and scripted pipelines, the Jenkinsfile living beside the application, shared libraries, Multibranch Pipeline building every branch, Blue Ocean, and the API for programmatic control.
Topics: Pipeline fundamentals · Declarative vs scripted pipeline · Jenkinsfile in source control · Shared libraries · Multi-configuration projects · Multibranch Pipeline · Blue Ocean · Jenkins API programming
We rebuild the agenda around the tools you actually run.
Request a custom agendaStand up Maven, Gradle and MSBuild jobs on a single controller with correct tool installations and agent targeting.
Attach agents of both platforms, label them, and route builds correctly — then observe queue behaviour when executors are saturated.
Configure authentication and folder-level authorisation so three teams share one controller without seeing each other's credentials.
Back up a fully configured Jenkins, destroy it, and restore configuration, credentials and build history from scratch.
Wire SonarQube, JUnit and JaCoCo so a coverage or quality regression fails the build and notifies the owning team.
Take an existing freestyle job, document its behaviour, convert it to a declarative Jenkinsfile, and extend it to Multibranch with a shared library.
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
Helped to understand more on overall DevOps concepts.
Got good lab sessions which kept the new DevOps tool learnings to the point and it helped a lot in my career.
I recently did a SRE Session with Rajesh Kumar from DevOps School and the session was great. Right from 1st day till day 15, we had a very interactive session. Rajesh clarified our doubts and the tool demos were excellent without any hiccups. He simplified the concepts while sticking to the content with a fine balance between theory and practice. Am convinced he is one of the best trainers for SRE & DevOps concepts.
The Rundeck developer session was excellent and highly engaging. I appreciated how well the session was structured, with the theoretical concepts explained clearly and in simple terms. What stood out most to me was the demo — it was both informative and enjoyable. I especially liked how Rajesh walked us through not only the happy path but also the sad path, showcasing common issues and sharing practical troubleshooting tips.
Rajesh's experience and knowledge are exceptional and we learnt invaluable practical knowledge which we can apply in our production environment. Incredibly friendly and gave us a fantastic insight both in-depth and at a high level of the Rundeck product.
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.
| 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 advisorDelivered onsite at your premises or live online in your timezone.
Prefer to call or email?
More ways to reach us on the contact page.