We're using Azure Pipelines for automating deploying our changes from the code in the repository to our production environment. We have a …
Azure Pipelines are used for any deployment of our apps, backend services and test automation. This is the backbone of our deployment …
We use Azure Pipeline in the applications that we do for IoT use cases for different retail companies in Europe and US. Azure Pipeline is …
Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of Azure Pipelines, and make your voice heard!
Entry-level set up fee?
- No setup fee
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
Would you like us to let the vendor know that you want pricing?
Users can automate builds and deployments with Azure Pipelines. Build, test, and deploy Node.js, Python, Java, PHP, Ruby, C/C++, .NET, Android, and iOS apps. Run in parallel on Linux, macOS, and Windows. Azure Pipelines can be purchased standalone, but it is also part of Azure DevOps Services agile development planning and CI/CD suite.
Companies can't remove reviews or game the system. Here's why
We're using Azure Pipelines for automating deploying our changes from the code in the repository to our production environment. We have a few pipelines for our separate environments. We're checking the quality of the changes that are going to be made and then if everything passes, we're doing a deployment.
- all in one place
- good ability to personalize deployment process
- easy to develop
- 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
It's good when you want to have an easy way to deploy your changes to the production environment. Furthermore, there are a lot of possibilities to add some tasks from different services, so it is easy to fit the pipeline to the case you have to have. When you need to have good error handling it is less appropriate.
Azure Pipelines are used for any deployment of our apps, backend services and test automation. This is the backbone of our deployment process allows us to deliver within our release cycle. Our current deployment cycle is monthly - but at times we may have smaller more controlled deployments within a release cycle. Azure Pipelines are fully integrated with our workflows as we also use Azure DevOps and implementation was more effective and efficient for us than other tools that might exist.
- Integration with SonarQube
- Integration with Azure DevOps
- Integration with GitHub
- Error messaging when team members don't have permissions
With a fully Microsoft Azure based workflow - Azure Pipelines makes absolute sense. Azure Pipelines are robust and work very well with SonarQube for test coverage and are shared with our developers. This prevents the developers for pushing code without unit tests across our backend and frontend platforms. We have reduced our instances of manual regression tests especially when there are multiple teams working across the same repositories.
We use Azure Pipeline in the applications that we do for IoT use cases for different retail companies in Europe and US. Azure Pipeline is used in the deployment of the resource groups. resources, web applications, and function apps. It is very helpful, especially the CI/CD pipeline for the web applications and function apps. It makes the developer's life easier.
- Continuous Integration
- Continuous Deployment
- ARM template deployments
- Difficult integration with Non-Microsoft
- Waiting time if parallel deployments are happening
Since we are consistently using Microsoft products, I have not used any pipeline of different companies but the Azure pipeline is suitable in our use case which is IoT. We do not have too many repeatable deployments but the CI/CD deployment is very helpful to make the work easier and faster.