Skip to content
Olivier DALET edited this page May 13, 2020 · 20 revisions

Continuous Integration

Cake

Example projects

Code Coverage

CI/CD

Github Actions

Azure DevOps


Azure DevOps vs Github Actions

Essentially, the GitHub Actions feature seems to be Azure Pipelines baked right into GitHub.

From a long term perspective, I'm curious about the future of GitHub as it pertains to Azure DevOps. Several speakers have described the GitHub community as "40 million collaborators to work with", so perhaps Microsoft intends to keep GitHub for open source projects, and Azure DevOps for private industry. We shall see.

I was wrong about GitHub Actions being just "Azure Pipelines baked right into GitHub".

In my previous post I challenged myself to convert my existing Azure DevOps Pipeline into GitHub Actions. So how did that work out?

What did not work (so well):

  • Build Numbers: GitHub Actions simply does not have the concept of build numbers.

  • No Build Variables: In GitHub Actions, there are no build variables per se.

Conclusion:

They do serve different purposes. GitHub is geared for Open Source projects, (...) GitHub will (and must) remain neutral. (...) Azure DevOps can promote the heck out of Microsoft Azure.

Gitlab + Windows

Clone this wiki locally