Looking to move off our current CI/CD platform. The pricing model just blew up after a "simple" upgrade, and I'm done with the surprise invoices. We're a lean team of 5 shipping a few Node.js APIs and a frontend to Azure App Service.
Need a tool that won't penalize us for parallel jobs or moderate build minutes. Azure DevOps Pipelines is the obvious candidate since we're already in the ecosystem, but I've heard the YAML can be a pain. GitHub Actions is the other contender, but I need to understand the real cost beyond the free tier.
My evaluation criteria:
* **Predictable pricing for a small team:** No per-user seat surprises after 5 users. Clear build minute costs.
* **Azure-native deployment support:** Service principals, Key Vault integration, App Service slots.
* **Low maintenance:** We don't have cycles to manage build agents ourselves.
Primary question: For those who made a similar choice recently, **what were the hidden costs or configuration pitfalls?** Specifically:
* Did you hit unexpected throttling or concurrency limits?
* Was secrets management a headache to migrate?
* How much time did the pipeline translation *actually* take?
Tempted by the "free" tiers, but I know they always get you later.
VendorNegotiator
Your point about pipeline translation time is key. When we moved from Jenkins to GitHub Actions for a similar Azure setup, I budgeted a week - it took three. The YAML itself was straightforward, but replicating our exact deployment orchestration with App Service slots and environment-specific Key Vault lookups required a lot of trial and error.
The hidden cost wasn't the tool, but the re-testing. Every pipeline change meant a full staging deployment to feel confident. And watch out for GitHub's concurrency limits on the free tier - if two commits push at once, one job queues. For a team of five it's usually fine, but on release day it can cause a frustrating bottleneck.
Secrets migration was actually simple with Azure's managed identities. The real pitfall was permissions - ensuring the Actions workflow identity had just enough access to the right Key Vaults and App Services. Took a while to get the Azure RBAC roles minimal and correct.
editor is my home
Pricing is the killer here, especially for parallel jobs. We stuck with Azure DevOps because the Microsoft-hosted parallel jobs are included in the basic plan ($30/user/month). For 5 devs, that's a flat $150, no build minute overages. With GitHub Actions, once you burn the free 3,000 minutes, you're buying extra packs and watching concurrent job limits.
Secrets migration was fine using Service Connections. The real time sink? Translating pipeline logic into that YAML. It's not hard, but getting conditional deployments and slot swaps exactly right took us two solid weeks, not days.
Have you looked at Azure DevOps' multi-stage YAML templates? They're verbose but once you build one, cloning it for your other services is trivial.
It's not marketing, it's logic.