AWS CodePipeline Reviews

I use the solution for CI/CD. We use it for continuous integration and delivery of our projects. It's primarily used to deploy applications to both development and live servers.

The tool's recent version helps us to run pipelines in parallel. The integration with other AWS services has greatly impacted our use of AWS CodePipeline. It made tasks such as integrating with Jira and provisioning instances much easier.

The tool's UI is wonderful. 

AWS CodePipeline functions well, but there's room for improvement in providing technical support to regular customers who haven't purchased developer support. I mean, having it available for everyone, even if it's not a 24-hour service. It would be more useful if specific support hours were available for assistance.

I have been using the product for nine months. 

I rate the tool's stability a ten out of ten. 

I rate the solution's scalability a ten out of ten. 

I have used GCP before. 

The tool's deployment is manageable. 

AWS CodePipeline is quite affordable. I've been running around four pipelines and the cost is around one dollar per month. It rarely exceeds two dollars.

I rate the tool a ten out of ten. 

Our primary use case for CodePipeline is speeding up our development process. The solution is highly automated and allows us to build and deploy code without any effort. It's automatically initiated once I commit my code. 

CodePipeline also helps me to find bugs quickly, increasing my release speed. On the other hand, it helps our customers receive our releases regularly and incrementally. CodePipeline helps us out with our delivery and our customers are happy to see our results in real time through it.

The solution is a continuous integration and delivery mechanism that helps us a lot in delivering our software. This is the most powerful benefit we get from using CodePipeline. It's one of those DevOps concepts recommended for use within the software development lifecycle.

I find performance to be the most valuable CodePipeline feature. It works perfectly and smoothly. We can also transition between the environments with CPLEX. I think CodePipeline is brilliant. 

CodePipeline allows you to focus on your program or your software, rather than worrying about deployment and the build stuff. We save quite a bit of time with CodePipeline.

The only area in my opinion that needs to be improved is the time between build and deployment. AWS should improve build time. We wait up to seven minutes for deployment.

In the next release, I would like to see fewer timeout errors.

I have been using AWS CodePipeline for around three years now.

I have had timeout errors in CodePipeline before. However, this has been acceptable for me as it was in development time and not in production.

My opinion is that this solution is scalable. It's good and it accepts a wide range of programming languages. I can manipulate the order and manage it regardless of the technology I'm using. It's very scalable. It's brilliant; a solution I like very much. It saves a lot of build and deployment effort if we compare it to old-style development. We consume a lot of time building and deploying, just to see our products running.

I have not contacted their tech support.

My impression is that this product is easy to set up. Everything including the documentation is provided.

I would recommend this solution to others as it is one of the most valuable products that can help any DevOps environment for software.

Overall, I would rate this solution a nine, on a scale from one to 10, with one being the worst and 10 being the best.

I am using AWS CodePipeline to deploy our products for production.

The most valuable feature of AWS CodePipeline is the flexibility of the configuration.

The solution could improve the documentation. Sometimes we have some issues with the documentation not updating after releasing .NET 6. We had some issues with building the code pipeline, and it was not updating the documentation. It's better to update the code documentation.

In a future release, they should improve the UX and add some additional features.

I have been using AWS CodePipeline for approximately three years.

AWS CodePipeline is stable once it is configured correctly.

We have four developers using this solution in my company.

The solution is scalable, we have multiple pipelines.

I have not contacted the support from AWS CodePipeline.

The initial setup of AWS CodePipeline is challenging because of the lack of updates to the documentation. The full implementation takes approximately two weeks.

We were using other Amazon solutions and this is why we chose AWS CodePipeline.

My advice to others is the implmentation process will take some time because of the poor documentation.

I rate AWS CodePipeline a six out of ten.

CodePipeline assists with the writing of code. It posts reports to our CodeCommit that is connected to our AWS source. 

In AWS, the Cloud DevOps is a managed service from CodeCommit and this has removed the need for a lot of manual steps. Using AWS Pipeline, we are able to add our requirements and it will be automatically scaled. This saves us time and connects to services like EKS. 

 AWS CodePipeline does a very good job as compared to Jenkins. We have saved money using this solution as we we pay for data as it is needed. AWS also offers great security.

I have been using this solution for one year. 

This is a very stable solution.

This is a scalable solution. There is also an option to autoscale. 

The customer service and support for this solution is good. 

Neutral

There are two key roles needed for the setup including the service role for AWS and the service role for CodePipeline. If there are many dependancies involved in the setup, it may take a long time. If a Docker file is already executed, the setup will be quicker. 

The pricing of this solution is dependent upon your needs including how many jobs you daily and how many times the developer will be changing codes and completing deployments.

I would rate this solution a nine out of ten.

We use CodePipeline for deploying some of the applications that we have for AWS.

Ours is a multi-cloud hybrid cloud approach. We have Azure, AWS, Google Cloud, and then we use CI/CD pipelines - our core pipeline tools - from each cloud. For example, on Azure, we use Azure DevOps that integrates with our GitHub on-prem. That's what we use for deploying anything on Azure. The same GitHub. It is also used on Google Cloud. We don't use the native tools from any of the clouds. For example, the CodePipeline from AWS or Deployment Manager from Google Cloud. We try to avoid those. We are moving towards Terraform with a GitHub integration as of our source code repository or pipeline, CI/CD pipeline. No matter what the cloud, we use our on-prem resources. We try to avoid using the cloud.

The solution is pretty stable. 

It's a perfect solution if you are just using AWS.

The pricing is okay.

Since we are very price-conscious, we would like the solution to be cheaper. If it was, we would use it more. 

CodePipeline is not an option for us at all, as CodePipeline is strictly tied to AWS and we have workloads on Azure and Google. We don't want our workloads to be running from source code that is running in AWS. That's why we prefer on-prem for source code with Terraform and GitHub and then use that to deploy across the cloud. That's our approach.

The last time we used the solution was for a project about a year ago.

The solution is pretty stable. Obviously, there are bugs dealing with it, however, it is a pretty good tool. It doesn't give us too many issues. 

Whenever we get a requirement for an application deployment in the public cloud, we usually compare if that service is available in all of the three clouds and then we run those pricing estimates to see which is cheaper on which cloud. I work as an enterprise company and we have multiple tabs from all three. Whoever gives us the cheaper credit, that's what we go with - which is cheaper.

I'd give it a ten out of ten. It's the best tool. It's good for AWS, however, if you're talking about multi-cloud, you can't use it.

We use the product for serverless integration AWS Lambda.

The product helps with testing the code. We can integrate it to build and deploy code. We can create an automation template as well.

AWS CodePipeline has valuable integration features.

The product could be integrated easily with other platforms, such as GitHub. The migration process from one source code to another needs improvement. It should support different codes and tools.

We have been using AWS CodePipeline for two years. At present, we use the latest version.

It is a stable platform. I rate its stability a ten out of ten.

I rate the product’s scalability a six out of ten.

The technical support team’s response time depends on the criticality of the issue.

We have used GitHub before. We switched to AWS CodePipeline for better security features while integrating with other platforms.

The configuration is difficult in the beginning. It becomes easier to deploy with the help of Terraform.

I rate AWS CodePipeline an eight out of ten.