⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All CI/CD & GitOps Interview Questions Scenario 94 of 187 in CI/CD & GitOps
Senior DevOps / SRE [L2] CI/CD 🔐 Supply Chain Security & Advanced CI/CD Production Scenario [L2]
🎯 Target Role / Context: CI/CD Scenario #85 (L2) · 🔐 Supply Chain Security & Advanced CI/CD

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:

#CI/CD #L2 #DevOps #Automation #Pipelines
🎙️ Candidate Opening & Architectural Context
""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.""
Advertisement
⚡ Recommended Practice Lab

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."

1️⃣

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: 7 on all artifacts to prevent indefinite storage accumulation.
2️⃣

Remediation & Permanent Safeguards

- uses: actions/upload-artifact@v4
  if: success() && github.ref == 'refs/heads/main'
  with:
    name: test-results
    path: ./results/
    retention-days: 7
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Conditional upload: Only upload artifacts when the job actually passes or when specifically triggered on main:."
⚡ 60-Second Elevator Pitch Talking Points
  • 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.
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. 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.
  2. 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.
  3. 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.
  4. 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.
Advertisement
Want more CI/CD & GitOps scenarios?
Explore our complete collection of scenario-based CI/CD & GitOps interview runbooks.
Browse All CI/CD & GitOps Questions →