Camp Fire Academy
Learning path
Complete UI/UX Masterclass UI/UX Design Foundations UI/UX Design Intermediate Advanced UX Strategy
Specialisations
Fintech & Banking UI/UX UI/UX with AI Training UX for Leaders Design Thinking Figma Training
Most requested
AI for Workplace Productivity Excel for Business Power BI & Business Intelligence Cybersecurity Awareness PDPA Compliance Data Protection Officer Browse the full catalogue →
For teams
Corporate & In-House Training LMS & Self-Paced Learning Events
Company
About Contact Verify Certificate WhatsApp

CI/CD & DevOps Culture

Teams usually buy a CI/CD tool before they change how they work, then find the tool did not fix the thing that was slowing them down. The bottleneck is more often a branching strategy that guarantees painful merges, a test suite nobody trusts, or a release process requiring three people and a weekend. This day covers the pipeline mechanics and gives equal weight to the practices around them, because one without the other does not produce faster or safer delivery.

Programme Agenda

What Actually Slows Delivery Down

Batch size, handoffs, manual gates and rework. Measuring lead time and change failure rate before deciding what to automate, so the automation goes where the delay is.

Branching and Integration

Trunk-based development against long-lived feature branches, and the merge cost each implies. Feature flags as an alternative to branching for incomplete work.

Pipeline Anatomy

Build, test, package, deploy. Stage design, fail-fast ordering, caching and parallelism, and keeping a pipeline fast enough that people do not work around it.

The Testing Layers

Unit, integration, contract and end-to-end tests: what each is good at and the cost of over-investing in the slowest layer. Flaky tests, and why tolerating one destroys trust in the whole suite.

Artefacts, Versioning and Environments

Building once and promoting the same artefact through environments. Versioning, immutability, and the configuration-per-environment pattern that avoids rebuilds.

Deployment Patterns

Rolling, blue-green and canary deployments compared on risk, cost and complexity. Automated rollback, and the health signal that triggers it.

Secrets, Access and Pipeline Security

Keeping credentials out of the repository and the log, scoping pipeline permissions, dependency and image scanning, and protecting the pipeline itself as production infrastructure.

Working Practice

Code review that improves code rather than delaying it, shared ownership of the build, on-call and incident review, and the metrics worth tracking as a team rather than reporting upward.

Learning Outcomes:
Measure delivery performance before choosing what to automate
Choose a branching strategy matched to your team's release cadence
Design a pipeline that fails fast and stays quick enough to be trusted
Balance the testing layers instead of over-investing in end-to-end tests
Build an artefact once and promote it through environments unchanged
Select a deployment pattern proportionate to the risk of the change
Keep secrets out of pipelines and treat the pipeline as production
Adopt the review and ownership practices that make the tooling pay off

Duration: 1 Day (8 Hours)
Training Hours: 9:00 AM to 5:00 PM
Level: All levels
Training Mode: Physical, Online, or Hybrid
HRD Corp SBL-KHAS Claimable
Certificate of Completion included

Frequently Asked Questions

Developers, QA engineers, system administrators, technical leads and engineering managers. Mixed teams from the same organisation get the most from it because the practice modules depend on shared context.

Examples run in a common hosted pipeline tool, but the material is deliberately tool-independent. The pipeline design, testing and deployment patterns transfer to whatever your organisation uses.

Partly. Participants build and modify a pipeline during the day, but a single day cannot be a full lab course. The emphasis is on design decisions and practice.

It helps but is not essential. QA, operations and management participants follow the pipeline work comfortably; the code involved is small and provided.

Yes, this programme is HRD Corp SBL-KHAS claimable. Our team can assist your HR department with the documentation required for the grant application.

Yes. Any programme can be booked as a team day. Everyone works the same brief together, so your people come away having built something and knowing each other better.

If you are claiming under HRD Corp, the session has to fall at least 14 days after your HRD Corp approval. If you are not claiming, the date is flexible and we work around your calendar.

Put them on the self-paced e-learning instead. Your team works through the modules on our LMS in their own time, sits the assessment, and earns the same certificate, so nobody has to clear a full day together.

More in Cloud, DevOps and Platform Engineering