I advise to go with test runs and see how everything is functioning. It's best not to integrate everything in one go. Challenges might arise while setting up initially. I'd rate the solution seven out of ten.
I would recommend it for at least medium, but especially enterprise level. They should go for AWS or Azure. Both are really fine and good. I currently work with four different customers as a technical architect for data migration and a couple of other projects. My recommendation is to go for AWS CI/CD and leverage AWS services. Overall, I would rate it a nine out of ten. I can recommend it to others.
Associate DevOps Engineer at a computer software company with 1-10 employees
Real User
Top 20
2024-06-25T07:09:48Z
Jun 25, 2024
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.
DevOps Engineer at a retailer with 501-1,000 employees
Real User
Top 20
2024-05-20T18:08:56Z
May 20, 2024
The configuration and setup of the tool are good areas. For now, I think the tool has more advantages than disadvantages. The tool is very easy to use for the setup, deployment, and continuous integration processes, so it is an effective product. There is not much need to maintain it. Initially, you need to know exactly how you want to map everything. I rate the tool a nine out of ten.
Sometimes, I use CodePipeline to integrate applications on my EC2 server. Sometimes, I use it with AWS Lambda. I am working as a DevOps engineer. I provide technical support to customers who are using the product. I have to demonstrate the customers' issues and try to resolve them. I recommend the solution to experienced people. If someone uses Amazon’s DevOps tool, I will recommend the solution. Otherwise, I will not recommend the product. Overall, I rate the product a seven to eight out of ten.
In addition to Maven, CodeBuild supports Gradle. Gradle builds have some issues. The tool provides more control over the underlying agent containers. Earlier, we used in-house products. I will recommend the solution if someone is using AWS. It comes with an entire ecosystem. Overall, I rate the solution an eight out of ten.
We have integrated AWS CodePipeline with AWS services such as Amazon EKS, ECS, and EC2 for virtual machine deployments. We can integrate it with Lambda for event triggering. It is a useful service. It is straightforward to understand for new users who are learning the application deployment through pipelines. While Jenkins requires installation, server setup, and security considerations, CodePipeline simplifies the process by handling the underlying infrastructure, allowing users to concentrate solely on pipeline scripts. I rate the product an eight out of ten.
People using the solution for the first time must have good experience in troubleshooting. If we do something wrong, we should be patient enough to solve it. We should not get frustrated. A good networking experience in AWS and a good knowledge of IP addresses will also be helpful. Overall, I rate the product a nine out of ten.
Senior ict specialist at Information& eGov Authority
Real User
Top 5
2023-01-06T17:02:42Z
Jan 6, 2023
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.
AWS CodePipeline is a fully managed continuous delivery service that helps you automate your release pipelines for fast and reliable application and infrastructure updates. CodePipeline automates the build, test, and deploy phases of your release process every time there is a code change, based on the release model you define. This enables you to rapidly and reliably deliver features and updates. You can easily integrate AWS CodePipeline with third-party services such as GitHub or with your...
I advise to go with test runs and see how everything is functioning. It's best not to integrate everything in one go. Challenges might arise while setting up initially. I'd rate the solution seven out of ten.
I would recommend it for at least medium, but especially enterprise level. They should go for AWS or Azure. Both are really fine and good. I currently work with four different customers as a technical architect for data migration and a couple of other projects. My recommendation is to go for AWS CI/CD and leverage AWS services. Overall, I would rate it a nine out of ten. I can recommend it to others.
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.
The configuration and setup of the tool are good areas. For now, I think the tool has more advantages than disadvantages. The tool is very easy to use for the setup, deployment, and continuous integration processes, so it is an effective product. There is not much need to maintain it. Initially, you need to know exactly how you want to map everything. I rate the tool a nine out of ten.
Sometimes, I use CodePipeline to integrate applications on my EC2 server. Sometimes, I use it with AWS Lambda. I am working as a DevOps engineer. I provide technical support to customers who are using the product. I have to demonstrate the customers' issues and try to resolve them. I recommend the solution to experienced people. If someone uses Amazon’s DevOps tool, I will recommend the solution. Otherwise, I will not recommend the product. Overall, I rate the product a seven to eight out of ten.
In addition to Maven, CodeBuild supports Gradle. Gradle builds have some issues. The tool provides more control over the underlying agent containers. Earlier, we used in-house products. I will recommend the solution if someone is using AWS. It comes with an entire ecosystem. Overall, I rate the solution an eight out of ten.
We have integrated AWS CodePipeline with AWS services such as Amazon EKS, ECS, and EC2 for virtual machine deployments. We can integrate it with Lambda for event triggering. It is a useful service. It is straightforward to understand for new users who are learning the application deployment through pipelines. While Jenkins requires installation, server setup, and security considerations, CodePipeline simplifies the process by handling the underlying infrastructure, allowing users to concentrate solely on pipeline scripts. I rate the product an eight out of ten.
People using the solution for the first time must have good experience in troubleshooting. If we do something wrong, we should be patient enough to solve it. We should not get frustrated. A good networking experience in AWS and a good knowledge of IP addresses will also be helpful. Overall, I rate the product a nine out of ten.
I rate AWS CodePipeline an eight out of ten.
I would rate the product an eight out of ten. If you have a multi-cloud infrastructure, then you need to consider Jenkins, GitLab or GitHub.
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.
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 would rate this solution a nine out of ten.
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.