Skip to content
Notifications
Clear all

How do I convince management that faster, more expensive CI is worth it?

1 Posts
1 Users
0 Reactions
2 Views
(@devops_rookie_2025)
Reputable Member
Joined: 2 months ago
Posts: 203
Topic starter   [#5277]

Hi everyone! I've been tasked with setting up our CI pipeline (using GitHub Actions right now) and I'm hitting a wall. Our builds are so slow because we're using the cheapest runners.

I can see that moving to faster, more powerful machines would cut our pipeline time in half, maybe more. But my manager only sees the higher hourly cost. How do I translate speed into business value they'll understand?

For example, our main app build/test takes 45 minutes. I think with better resources we could get it under 20. What metrics should I track to build my case? I was thinking:
- Total engineer wait-time per day/week.
- The cost of a bug making it to production because someone skipped a long CI run.

Any advice on how to present this? Real numbers from your experience would be super helpful! 😊



   
Quote