- The situation at Fernhill Home
- Your role and the brief
- Environment and starter files
Recover a failing delivery pipeline before release day
Fernhill Home’s release pipeline has not been green for a week and nobody trusts what it ships. You recreate the broken GitHub Actions pipeline, diagnose each failure from its log, fix the build, tests and container image, publish tagged images to a registry, add a scanned and gated staging deploy, and prove you can roll back in minutes.
PCREATED BYPrepmeetsProject studio, Prepmeets
THE CHALLENGE → YOUR OUTCOME
Real context. Work that matters.
Fernhill Home’s catalogue service has a release on Friday and a pipeline nobody has seen pass in a week. You rebuild the failure, work out why each stage breaks, make the tests deterministic, publish immutable SHA-tagged images, scan them, deploy the exact tested image to a gated staging step, and rehearse a rollback with a stopwatch.
What’s at stake
Your responsibility: Work as the platform engineer, delivery team—investigate the requirements, implement your approach and verify the result.The catalogue service feeds the website’s product pages. Its pipeline was copied from a blog post three years ago and has been patched ever since. Last week a dependency bump turned it red. Two engineers have since pushed images from their laptops to “keep things moving”, so nobody can say exactly what is running in staging.
Success means: A pipeline whose green means tested: deterministic tests on two Node versions, an image built once from a pinned base, scanned, tagged with its commit SHA and pushed, a staging step that runs that exact tag behind an environment gate, and a rollback that is a single run you have timed. Explain the decisions and checks behind your implementation.
WHAT YOU’LL BUILD
01GitHub Actions
02CI/CD
03Docker
Fernhill Home catalog-api and its pipeline
INCLUDED WITH YOUR PROJECT
A workspace, not just a document.
Your brief, a Jira-style task board and an interview studio—all in one place.
A look inside your workspace
Start with the full project brief
Build step by step Track your progress Own your interview story
Know where you’re heading.
- 01The situation at Fernhill Home
- 02Your role and the brief
- 03Environment and starter files
- 04The two loops
- 05Reproduce, classify, fix, ship, roll back
- 06Break it on purpose
- 07What you hand over
- 08Submission and cleanup
Practise explaining your decisions
Which decision mattered most in your solution, and how did you verify it?
Use your own implementation to connect Situation, Task, Action and Result into one interview story.
Before you begin · tools & running costs
Prerequisites: Your own accounts and access to GitHub Actions, Docker and a multi-stage Dockerfile, GitHub Container Registry, Trivy image scanning.
Additional costs: Cloud and tool usage in your own accounts may incur charges. Set a budget and clean up after testing.
Work in your own accounts and repositories. Never share credentials or confidential data.
What’s included
Project brief, target-design guidance, assigned tasks, resource guidance and interview prompts. Detailed requirements become part of your purchased workspace.
P
MEET YOUR PROJECT EXPERT
Prepmeets
Project studio, PrepmeetsWe are the team that builds Prepmeets. Between us we have run cloud platforms, delivery pipelines, analytics teams and AI governance programmes in banks, hospitals, retailers and government departments, and these projects are the work we used to hand to new joiners in their first fortnight. Every one of them is a real scenario with the client’s name changed, scoped to a week of evenings, and reviewed by the person who originally did the job.
View verified expert profile Expert review is an optional paid service, separate from project access.
£19.90Start this project