QA Workflow
Pipeline Signals: CI for QA Discipline
Read build noise, gate releases responsibly, and talk to platform folk without jargon sludge.
Evening broadcast Advanced GitHub Actions
3 weeks · 12 live hours
KRW 520,000 · informational reference
What happens inside
This workflow course sits between pure automation and release management. You will map quality signals in CI, design flaky-test policies, and practice writing RFC-grade recommendations when pipelines need restructuring—not just more scripts.
Included cadence
- ↗ SLI/SLO vocabulary tuned for testers
- ↗ Red/yellow/green policy worksheet
- ↗ Sample GitHub Actions graph to annotate
- ↗ Async role-play: you brief a mock engineering manager
- ↗ Office hours on artifact storage costs
- ↗ Template for weekly release health memo
- ↗ Office hours transcript pack
Outcomes you can audit
Draft a pipeline risk brief with two measurable gates.
List three artefacts your team should stop hoarding.
Facilitate a fifteen-minute triage on failing jobs.
Straight answers
Is this about writing YAML all day?
Some reading, but focus is decision-making and communication—not authoring every step.
Bare metal servers?
Examples assume cloud-hosted runners; adapt principles with your platform team.
One-on-one coaching?
Not included; pair sessions are group-based to keep cohort energy high.
Participant notes
“Pipeline Signals reframed flaky tests as inventory, not shame. Our weekly memo now lands in Slack without eye rolls.”
“Short, punchy. Wanted another week on observability taps—still useful.”