Likelihood to Recommend 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
Read full review Previously, our team used
Jenkins . However, since it's a shared deployment resource we don't have admin access. We tried GoCD as it's open source and we really like. We set up our deployment pipeline to run whenever codes are merged to master, run the unit test and revert back if it doesn't pass. Once it's deployed to the staging environment, we can simply do 1-click to deploy the appropriate version to production. We use this to deploy to an on-prem server and also AWS. Some deployment pipelines use custom Powershell script for.Net application, some others use Bash script to execute the docker push and cloud formation template to build elastic beanstalk.
Read full review Pros Integration with SonarQube Integration with Azure DevOps Integration with GitHub Read full review Pipeline-as-Code works really well. All our pipelines are defined in yml files, which are checked into SCM. The ability to link multiple pipelines together is really cool. Later pipelines can declare a dependency to pick up the build artifacts of earlier ones. Agents definition is really great. We can define multiple different kinds of environments to best suit our diverse build systems. Read full review Cons 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 Read full review UI can be improved Location for settings can be re-arranged API for setting up pipeline Read full review Alternatives Considered 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
Read full review GoCD is easier to setup, but harder to customize at runtime. There's no way to trigger a pipeline with custom parameters.
Jenkins is more flexible at runtime. You can define multiple user-provided parameters so when user needs to trigger a build, there's a form for him/her to input the parameters.
Read full review Return on Investment we have had outages from Azure in the past Read full review ROI has been good since it's open source Settings.xml need to be backed up periodically. It contains all the settings for your pipelines! We accidentally deleted before and we have to restore and re-create several missing pipelines More straight forward use of API and allows filtering e.g., pull all pipelines triggered after this date Read full review ScreenShots