Q: Your GitHub Actions workflow is taking 18 minutes because it uploads a 4GB test artifact to GitHub Artifacts storage after every run, even for PRs that fail. How do you reduce pipeline cost and duration with minimal code changes?
Two immediate improvements:
Want to master this scenario in a live sandbox? KodeKloud's Enterprise GitOps with ArgoCD & Kubernetes Rollouts covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "In our delivery pipeline supporting multiple engineering squads, pipeline reliability was paramount. The interviewer is testing: Conditional artifact uploads, artifact retention policies.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
Two immediate improvements:
- Conditional upload: Only upload artifacts when the job actually passes or when specifically triggered on
main: - Reduce artifact size: Archive only the failed test reports, not the entire output directory. For a 4 GB binary artifact, push it to S3 directly from the workflow instead of GitHub Artifacts storage — it's 10× cheaper and not subject to GitHub's storage quotas.
- Set
retention-days: 7on all artifacts to prevent indefinite storage accumulation.
Remediation & Permanent Safeguards
- uses: actions/upload-artifact@v4
if: success() && github.ref == 'refs/heads/main'
with:
name: test-results
path: ./results/
retention-days: 7
- Conditional upload: Only upload artifacts when the job actually passes or when specifically trigg...
- Reduce artifact size: Archive only the failed test reports, not the entire output directory. For ...
- Set retention-days: 7 on all artifacts to prevent indefinite storage accumulation.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Promoting application releases to production without an automated, canary-validated rollback mechanism when configuring GitHub Actions workflow Pipelines that lack automated rollback mechanisms force engineering teams to scramble manual hotfixes during severe production regressions.
- Running concurrent deployment pipeline jobs without stage mutex locking on shared target environments when configuring GitHub Actions workflow Concurrent pipeline runs on the same environment race to apply state changes, causing out-of-order commits and unpredictable deployment state.
- Omitting dependency lockfiles (package-lock.json, go.sum, Cargo.lock) from continuous integration builds when configuring GitHub Actions workflow Omitting lockfiles allows upstream package updates to break builds unpredictably without any changes to application codebase.
- Failing to define dynamic cache invalidation keys for CI package managers and layer caches when configuring GitHub Actions workflow in ci-cd-q085-your-github-actions-workflow-is-tak Stale build caches mask underlying dependency incompatibilities or pull outdated libraries, while un-cached runs slow feedback loops.