AWS CodePipeline is a fully managed continuous delivery service that helps users automate release pipelines for fast, reliable application and infrastructure updates. CodePipeline automates the build, test, and deploy phases of the release process every time there is a code change, based on the release model a user defines. This is to enable rapid, reliable delivery of features and updates. Users can integrate AWS CodePipeline with third-party services such as GitHub or with a custom plugin. AWS…
$1
per active pipeline/per month
Azure DevOps Services
Score 8.5 out of 10
N/A
Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
Pricing
AWS CodePipeline
Azure DevOps Services
Editions & Modules
AWS CodePipeline
$1
per active pipeline/per month
Free Tier
Free
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
Basic + Test Plan
$52
per user per month
Offerings
Pricing Offerings
AWS CodePipeline
Azure DevOps Services
Free Trial
No
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
AWS CodePipeline
Azure DevOps Services
Considered Both Products
AWS CodePipeline
No answer on this topic
Azure DevOps Services
Verified User
Engineer
Chose Azure DevOps Services
Azure DevOps required the least amount of up front knowledge to get a pipeline up and running. Because of the built in activities, when I initially started working with this tool I didn't have to know anything other than where my code was stored. The rest was easy enough to …
AWS CodePipeline is a continuous delivery tool used to model and automate software releases, particularly when a CI / CD pipeline relies on at least some AWS products and resources. It can integrate Git repositories like GitHub or AWS CodeCommit, build automation services like CloudBees, Jenkins, or AWS CodeBuild, and testing tools like BlazeMeter. Azure DevOps Services, on Microsoft Azure, is an agile development suite of tools replacing the former VSTS, featuring Azure Pipelines, a service quite similar to but slightly more robust than AWS CodePipeline, alongside agile project space Azure Boards, and Azure’s own repo tools and Azure Test Plans testing toolkit. Both CodePipelines and Azure DevOps with Azure Pipelines are used to orchestrate a CI / CD pipeline in the cloud. Both solutions are deployed across companies of all sizes, and somewhat more at larger companies.
Features
For continuous delivery in the cloud, AWS and Azure DevOps both present some clear advantages.
When building with Azure DevOps, users will reside in a rich ecosystem of apps and serviceable integrations (Chef, GitHub), while having complete in-built CI / CD automation (Azure Pipelines), as well as a strong agile planning tool with Azure Boards. Few competitors can boast breadth of services equal to Azure DevOps. With its native tool for managing teams using agile, waterfall, or hybrid methodologies, Microsoft Azure’s DevOps Services presents a flexible and complete solution.
AWS CodePipelines provides easy integrations with AWS tools, infrastructure and services, and provides the user with either a graphical user interface and setup wizard for modeling the software release process or infrastructure as code via AWS CloudFormation configuration tool; both the in-built graphical interface and the integratable IAC option are highly regarded. A straightforward tool, CodePipelines receives high marks for its core capabilities.
Limitations
There are a few limitations when using Azure DevOps Services or AWS CodePipelines worth mentioning.
AWS CodePipelines does what it does, and little more; users do not like it for building with services outside the AWS ecosystem. In fact, the benefits of working with AWS CodePipelines is directly related to how many AWS services you are using.
Likewise, the greatest limitation of Azure DevOp Services is that the Azure cloud where it resides is not appropriate for every agile project. Additionally, administrators complain about user and team management, access controls, UI quibbles (e.g. lack of clear placement of tools), as well as customizability.
Pricing
AWS CodePipelines is delivered on a pay for what you use model, with the price being $1.00 per active pipeline per month (i.e. it has at least one active code change through the month and has existed for at least 30 days). Pipelines are free up to 30 days from creation. Azure DevOps Services are free for the first 5 users on a team, and then $6 per user subsequently. Azure Pipelines activity is priced so that for Microsoft Azure hosting the first 1800 minutes are free for one parallel job, then $40 for each parallel job with unlimited minutes. The first parallel job is free with self-hosting, with each subsequent one costing $15 dollars. Azure Artifacts are free for the first 2GB, and then $2 for each extra GB.
I think AWS CodePipeline is a great tool for anyone wanted automated deployments in a multi-server/container AWS environment. AWS also offers services like Elastic Beanstalk that provide a more managed hosting & deployment experience. CodePipeline is a good middle ground with solid, built-in automation with enough customizability to not lock people into one deployment or architecture philosophy.
ADO is well suited for the visibility of day-to-day tasks and responsibilities as well as things such as Features, user stories, etc. Off the top of my head, I can't think of any scenario where it might not be well suited, as you can customize ADO to your liking to a degree.
Flexible Requirements Hierarchy Management: AZDO makes it easy to track items such as features or epics as a flat list, or as a hierarchy in which you can track the parent-child relationship.
Fast Data Entry: AZDO was designed to facilitate quick data entry to capture work items quickly, while still enabling detailed capture of acceptance criteria and item properties.
Excel Integration: AZDO stands out for its integration with MS Excel, which enables quick updates for bulk items.
I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.
Overall, I give AWS Codepipeline a 9 because it gets the job done and I can't complain much about the web interface as much of the action is taking place behind the scenes on the terminal locally or via Amazon's infrastructure anyway. It would be nicer to have a better flowing and visualizable web interface, however.
Azure DevOps is a powerful, complex cloud application. As such there are a number of things it does great and something where there is room for improvement. One of those areas would be in usability. In my opinion it relies too much on search. There is no easy way to view all projects or to group them in a logical way. You need to search for everything.
Our pipeline takes about 30 minutes to run through. Although this time depends on the applications you are using on either end, I feel that it is a reasonable time to make upgrades and updates to our system as it is not an every day push.
We didn't need a lot of support with AWS CodePipeline as it was pretty straightforward to configure and use, but where we ran into problems, the AWS community was able to help. AWS support agents were also helpful in resolving some of the minor issues we encountered, which we could not find a solution elsewhere.
When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.
CodeCommit and CodeDeploy can be used with CodePipeline so it’s not really fair to stack them against each other as they can be quite the compliment. The same goes for Beanstalk, which is often used as a deployment target in relation to CodePipeline.
CodePipeline fulfills the CI/CD duty, where the other services do not focus on that specific function. They are supplements, not replacements. CodePipeline will detect the updated code and handle deploying it to the actual instance via Beanstalk.
Jenkins is open source and not a native AWS service, that is its primary differentiator. Jenkins can also be used as a supplement to CodePipeline.
Microsoft Planner is used by project managers and IT service managers across our organization for task tracking and running their team meetings. Azure DevOps works better than Planner for software development teams but might possibly be too complex for non-software teams or more business-focused projects. We also use ServiceNow for IT service management and this tool provides better analysis and tracking of IT incidents, as Azure DevOps is more suited to development and project work for dev teams.
CodePipeline has reduced ongoing devops costs for my clients, especially around deployment & testing.
CodePipeline has sped up development workflow by making the deployment process automated off git pushes. Deployment takes very little coordination as the system will just trigger based on what is the latest commit in a branch.
CodePipeline offered a lot of out-of-the-box functionality that was much simpler to setup than a dedicated CI server. It allowed the deployment process to built and put into production with much less and effort and cost compared to rolling the functionality manually.
