Develop the checks that make a delivery pipeline useful.
Technology & digital skills
DevOps. From a code change to a controlled release.
Connect development and operation through a repeatable delivery process. Learn how a change is built, tested, deployed, observed and recovered when something goes wrong.
This is a learning-path guide, not a confirmed course intake. Ask about current availability, syllabus, delivery format, entry requirements, fees and assessment before applying.
Ask about training availabilityStart with a small application.
You will get more from DevOps practice if you can read a small application, use basic command-line tools and understand a version-control change. Deep knowledge of every platform is not the starting requirement.
Ask which environment the programme uses and whether accounts, cloud usage or external services carry additional costs. Begin with a bounded practice application rather than production credentials.
Topics to agree in the syllabus.
The stages should connect into one traceable path. Learning isolated commands is less useful than understanding what each step protects.
- Source control: changes, review, version history and a clear starting point.
- Build and checks: repeatable dependencies, tests and a usable build artifact.
- CI/CD: automated checks, deployment conditions and protected configuration.
- Environments: separation, secrets handling and an understandable configuration model.
- Operation: health signals, logs and recognition of a failed release.
- Recovery: rollback, verification and the person responsible for the next decision.
A practical project to discuss.
Take a small sample application from a repository to a test environment. Add an automated check that blocks a deliberately broken change, then deploy a corrected version.
Introduce a controlled deployment failure and work through the recovery instructions. The exercise should show which version is running and how the operator knows the service is healthy again.
Leave a usable delivery record.
A reviewer should be able to follow the route from source change to running version.
- A repository with readable change history and a simple review process.
- A pipeline definition and a record of successful and blocked runs.
- Documented environment settings with no secrets committed to source.
- A deployment and rollback runbook.
- A release record showing the version, checks and recovery result.
Measure repeatability.
Ask another learner to run the documented process in the agreed test environment. If the original author must supply hidden steps, the handover needs improvement.
Assess the response to a failed check or deployment as well as the successful path. A delivery pipeline supports control; it does not remove the need for acceptance criteria, operational judgement or a person who owns release decisions.
Start with your
actual requirement.
Tell us the work, people and outcome you have in mind. We’ll confirm current scope and availability before agreeing the next step.