The Pipeline Is Slow. Skip Tests to Ship?
A 40-minute pipeline is blocking releases. A teammate wants to skip the test stage to ship faster. Defend your call.
Answer key reviewed by Branko Petric
Read first: Building a CI Pipeline with GitHub Actions
Your decision
Your deploy pipeline takes 40 minutes, and the team is frustrated. A teammate proposes skipping the test stage so releases ship faster. Do you agree, and what do you do instead?
The situation
Your CI/CD pipeline takes about 40 minutes end to end, and the test stage is the slowest part. The team is frustrated that every release waits on it, and momentum is stalling.
Context
The test stage runs unit, integration, and end-to-end suites serially on a single runner with no caching. A teammate proposes removing the test stage from the deploy pipeline so releases go out immediately, arguing developers can just test locally.
Related challenges
- After an Outage, Mandate Manual Approval on Every Deploy?
After a bad deploy caused an outage, leadership wants a mandatory human sign-off on every production release. Defend a better way to prevent the next one.
- It Is Just a Config File. Push It to Every Region at Once?
A generated rules file reached every edge proxy in every region within seconds, crashed all of them at once, and now the team wants a fix. Defend how config should ship.
- 3 AM Outage: Roll Back or Fix Forward?
A deploy 20 minutes ago correlates with a spike in 500s. You are on call. Defend whether to roll back or fix forward.
- Tests Pass Locally, Fail in CI. Just Retry?
Your suite is green on your laptop but red in CI. A teammate wants to add a retry and re-run until green. Defend what you actually do.