I'm choosing a CI/CD platform in 2022 and the decision between Azure DevOps and GitHub Actions isn't straightforward. Microsoft owns both, but the choice depends on factors that aren't immediately clear from the product descriptions.
Azure DevOps has some significant strengths. Its Pipelines have matured quickly, with better variable groups and pipeline templates in YAML, solid package management through Azure Artifacts, and classic release pipelines for a graphical approval approach. If I'm already using Azure Boards for agile management, keeping my CI/CD in the same place saves me from constant context switching.
One area where Azure DevOps excels is in its support for complex deployment scenarios. For example, I can use Azure DevOps to deploy to multiple environments, with different configurations for each environment. This is particularly useful for teams that have multiple applications or services to deploy. I've seen teams use Azure DevOps to deploy to on-premises environments, as well as to cloud environments like Azure and AWS.
On the other hand, GitHub Actions has its own set of advantages. Since it lives in my repository, workflows are right next to my code, and the Marketplace has thousands of community actions available. OIDC for cloud auth is also more polished, making it a great choice if I'm doing open source work or using GitHub for code review.
When evaluating GitHub Actions, I've noticed that the community actions available in the Marketplace can save a lot of time. For instance, I can use a community action to deploy my application to AWS, without having to write custom code. However, I've also seen cases where community actions don't quite work as expected, requiring additional troubleshooting and customization. In one case, I had to modify a community action to work with our specific use case, which took a few hours of debugging.
If I'm considering migrating from Azure DevOps to GitHub Actions, I need to think about translating my YAML, swapping DevOps tasks for Marketplace equivalents, and migrating artifacts if I'm using them. It's not a trivial process, but it's also not incredibly difficult for most setups.
The real question is whether the advantages of GitHub Actions justify the effort of migrating my workflows. For some teams, the integration with GitHub and the availability of community actions will be a major draw, while others may prefer the more traditional approach of Azure DevOps.
I've been using Azure DevOps for a while now, and I have to say that the pipeline templates in YAML are really useful. But at the same time, I can see the appeal of having my workflows right next to my code in GitHub.
In terms of cost, both platforms offer free plans, but Azure DevOps has some limitations on the number of concurrent jobs and pipeline runs. GitHub Actions, on the other hand, offers more generous free limits, but requires a GitHub repository. For small teams or open-source projects, GitHub Actions may be a more cost-effective option. For larger teams or enterprises, Azure DevOps may be a better choice, especially if they're already using other Azure services.
In the end, the choice between Azure DevOps and GitHub Actions depends on my specific needs and workflow. Both platforms have their strengths and weaknesses, and it's up to me to decide which one is the best fit for my team.
As I weigh my options, I'm considering the trade-offs between the two platforms. Azure DevOps offers a more traditional approach to CI/CD, while GitHub Actions provides a more modern and integrated experience.