AWS CodePipeline Reviews

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 use the solution in my company, and we implement it whenever the tool is required in a project.

The need for the tool depends on the requirement. Some customers require closed and compact CI/CD pipelines; in such cases, we prefer AWS CodePipeline as the best option since it will be in a suitable environment. If the customers want some free sources, we can go with free sources. In our company, we have multiple CI/CD tools as well, but that completely depends on how much security the customers require and how much of a closed environment is required. AWS CodePipeline has some of the best features provided. The tool provides ample options, so we can use AWS Secrets Manager on those things where we can use AWS STS for some of the things, which will be much more helpful when working with a closed and secured environment.

Actually, the tool has multiple valuable features. When it comes to security, we have ample options to secure credentials, or whatever crucial data is there that is not supposed to be exposed. We can keep things in multiple environments, so we can create some environment variables from AWS Secrets Manager. From the environment variables, we can create different environments. The aforementioned area consists of one of the best features of the tool. Regarding additional features, we can use cross-account deployment, one of the tool's best features. When it comes to cross-account deployment, keeping one centralized account and deploying multiple applications in a different account is trending nowadays.

I have not thought about what needs improvement in the tool, but as of now, I am good with the tool. I am satisfied with the tool's performance, and I never came across any feature that it doesn't have. Whenever the customer requires something from the tool, all the features are present in AWS CodePipeline. If there is any option available in AWS CodePipeline that can offer integration with different products like SonarQube instead of just having to provide some URLs to our customers, then that would be great. It will make it easy for the integration of code analysis, and things can be done easily. I want to see more integration options. The industry doesn't go for paid versions, like CodeGuru, and some of the industries expect us to implement or integrate their tools with free products like SonarQube, which is supposed to provide a very free and basic structure. One would rather go for SonarQube rather than CodeGuru or other such tools. It would be best if AWS CodePipeline provided multiple integration options directly by providing some URLs.

I have been using AWS CodePipeline for two years. My company has a partnership with Amazon.

I have not seen any bugs in the tool. Its performance is quite good, which is similar to how any other CI/CD tool is supposed to perform.

Many people in my company use the product, but since it is a service-based company, everything completely depends on the choices and selections made. We are just here as a mentor to give suggestions and explain the advantages of what you get if you use AWS CodePipeline, Jenkins, and other such tools to our customers. In our company, we just give guidance on the importance of each tool to our customers, but selecting a CI/CD tool depends on the customers based on their budgets and their use cases. But we prefer CI/CD because it's a compact environment where there are fewer vulnerabilities. There is not much hard coding, and there is much more security, which is a more secure manner for the CI/CD pipeline.

Around 80 percent of my company's customers prefer AWS CodePipeline.

Scalability or other such factors don't have an impact on the product. AWS CodePipeline is a CI/CD tool that takes care of continuous integration and deployment. Where you are supposed to deploy the things, like if you are deploying at the cluster level, for your applications, there may be a need for auto-scaling. For CI/CD, you generally don't require any auto-scaling.

I haven't spoken to the tool's support team about CI/CD and other such areas. Things. Our company has recognized the advantages of AWS. We normally have some discussions with AWS' support team, but it is all associated with issues at the production level whenever it goes beyond our limits. We have a word with AWS' support team. For CI/CD, we don't contact AWS, but we are capable of managing it.

In our company, we normally don't use the installation process directly. It is one of the services we can directly build. As we are not performing in an on-premises model and are mostly at the cloud level, there are not many requirements. It is just a matter of a few clicks that will be needed to set up and keep the tool ready. If you come to CloudFormation in Terraform, things are not very difficult, and we can easily do it.

I haven't come across any challenges when setting up the product.

The price of the product depends on how many times you run it. The tool offers a pay-as-you-go model. The CI/CD pipeline can be considered as something that gets triggered per day at least four to five times, but sometimes, for the triggering part, there will be a certain amount that will be there. If the triggering is for a purpose, the user will incur a cost, but setting up the things won't cost anything.

Whether I would recommend the product to others or not is something that depends on whether you have multiple deployments and multiple cross-account integrations and if many other things are there for the application. If you are using just standard deployment using VCS, then I would suggest that you go with AWS CodePipeline. If you just want a simple single application deployment, then I prefer that you go for Jenkins, which is free of cost or open source. If one is keeping a centralized account for deploying multiple accounts of your application, I suggest you use AWS CodePipeline.

It is very easy to learn to use the product, and it is not a big deal since you need to just set up the things, and writing in buildspec YAML is not a big deal. Anyone can do it, even if you have an additional feature, such as restricting access to AWS CodePipeline by providing YALM. AWS CodePipeline is easier than Jenkins. Writing in pipeline scripts is something that people feel can be very difficult, but with buildspec YAML, it's quite easy to build it and add some logic, making it a process that is much easier compared to all CI/CD tools.

Different applications can be enhanced with AWS CodePipeline.

I rate the tool a nine out of ten.

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.

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.

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. 

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.

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.