Azure Pipelines vs. Buildkite

It is good tool if you are doing continuous improvements in your code and you wish it goes live whenever you push code to GitHub. So integrating Azure Pipeline, it automatically does CI/CD in the background once you push code/merge code and it is live in few minutes. It also does some automated tests if you have wrote scripts

Incentivized

I would definitely recommend Buildkite for anyone who needs a decent CI solution for 50+ on AWS instance without paying huge amount for AWS Build and code deploy tools.

Incentivized

• Integration with SonarQube
• Integration with Azure DevOps
• Integration with GitHub

Incentivized

• CI Solution
• Notification
• Configuration

Incentivized

• The errors which we got sometimes are not clearly enough.
• There are some let's say hidden options, they could be more visible
• When the process is running we have to remember about manually refreshing to see the current status because it doesn't work automatically

Incentivized

• Integration can be improved
• Cost reporting can be impoved

Incentivized

We have used the GitHub CI/CD. Earlier we were using the Azure Pipelines but after GitHub had their actions, we integrated that for CI/CD. It runs the tests and makes a production build which can be live. GitHub CI/CD is more useful because we have to make script only once then just by few changes we can deploy it onto Azure, AWS, Google anywhere so we found it more convenient

Incentivized

Buildkite was easy to use and setup while comparing Circle CI or GitHub. Additionally Buildkite was very affordable for teams while comparing GitHub plans

Incentivized

• we have had outages from Azure in the past

Incentivized

• Faster Build time
• Increased productivity

Incentivized