The documentation for AWS CodePipeline is lacking and makes it difficult to find information due to its complexity. It would be helpful to have examples in the documentation for different project types like Laravel or Django.
AWS CodePipeline works effectively, and I haven't identified any specific areas needing improvement as it has been quite satisfying in terms of deployment needs. Feedback from clients has also been positive, indicating satisfaction with the service.
From my perspective, some in-built capabilities could be enhanced. For example, SMS notifications should be integrated directly into the service. Currently, if I want to send an email notification when a pipeline or service fails, I need to configure it separately and hook it in. A couple of similar functionalities seem to be embedded within Jenkins CI/CD pipelines. Additionally, a more comprehensive UI would be beneficial, one that visually represents the progress of the pipeline execution. If a pipeline has ten steps, I should be able to see the execution in real-time as each step progresses. So, I'm expecting that an AWS monitoring-like control where I can track which steps are being executed, view the populated logs, and even have email notifications sent to stakeholders or agents as needed. These out-of-the-box capabilities would significantly streamline the development process. So, I would like to see in-built capabilities to populate the logs and some kind of log analysis to determine whether the job failed or passed. Based on that, notifications should be sent to other stakeholders.
Associate DevOps Engineer at a computer software company with 1-10 employees
Real User
Top 10
Jun 25, 2024
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.
DevOps Engineer at a retailer with 501-1,000 employees
Real User
Top 10
May 20, 2024
AWS continuously improves the tool's UI. One downside in AWS is that when you attempt to push a change in, it misses that part, or it could be because some variables are not set correctly. When AWS CloudFormation Stack goes for an update, it gives a failed status. Most of the time, you have to delete the stack and run your pipeline to create a new stack. You can't go back to reverse those changes with the AWS pipeline if a stack fails when you've pushed a change that didn't match up so well. It is not true that our company doesn't have a backup solution, which will help save everything in case something goes wrong. It is not that a backup is missing but more of a configuration based on how AWS CodePipeline is set up, like how AWS CloudFormation works.
There is limited room for tuning beyond the timeouts, memory, or CPU allocations. Sometimes, we need to take some screenshots of the results. The tool does not provide automated features for evidence collection. We must manually modify them to place them in S3 buckets and configure them.
There could be a possibility of deploying tag-based conditions for different environments using the same code base similar to GitHub. Implementing tag-based conditions in the build spec file is possible, but the process can be simpler. They could provide this tagging functionality in the UI itself. The users could decide pipeline triggers based on the predefined rules.
The setup time is a bit long. We need a lot of experience to work with it. We need a lot of troubleshooting experience. We need to contact support if things get out of hand.
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.
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.
Senior ict specialist at Information& eGov Authority
Real User
Jan 6, 2023
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.
Virtualization and Cloud Architect at a transportation company with 10,001+ employees
Real User
Aug 18, 2021
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.
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...
The documentation for AWS CodePipeline is lacking and makes it difficult to find information due to its complexity. It would be helpful to have examples in the documentation for different project types like Laravel or Django.
AWS CodePipeline works effectively, and I haven't identified any specific areas needing improvement as it has been quite satisfying in terms of deployment needs. Feedback from clients has also been positive, indicating satisfaction with the service.
A bit more control over AWS CodePipeline would make it a better tool. Improved enhancements and features could make it more intuitive.
From my perspective, some in-built capabilities could be enhanced. For example, SMS notifications should be integrated directly into the service. Currently, if I want to send an email notification when a pipeline or service fails, I need to configure it separately and hook it in. A couple of similar functionalities seem to be embedded within Jenkins CI/CD pipelines. Additionally, a more comprehensive UI would be beneficial, one that visually represents the progress of the pipeline execution. If a pipeline has ten steps, I should be able to see the execution in real-time as each step progresses. So, I'm expecting that an AWS monitoring-like control where I can track which steps are being executed, view the populated logs, and even have email notifications sent to stakeholders or agents as needed. These out-of-the-box capabilities would significantly streamline the development process. So, I would like to see in-built capabilities to populate the logs and some kind of log analysis to determine whether the job failed or passed. Based on that, notifications should be sent to other stakeholders.
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.
AWS continuously improves the tool's UI. One downside in AWS is that when you attempt to push a change in, it misses that part, or it could be because some variables are not set correctly. When AWS CloudFormation Stack goes for an update, it gives a failed status. Most of the time, you have to delete the stack and run your pipeline to create a new stack. You can't go back to reverse those changes with the AWS pipeline if a stack fails when you've pushed a change that didn't match up so well. It is not true that our company doesn't have a backup solution, which will help save everything in case something goes wrong. It is not that a backup is missing but more of a configuration based on how AWS CodePipeline is set up, like how AWS CloudFormation works.
The support team’s response time must be improved.
There is limited room for tuning beyond the timeouts, memory, or CPU allocations. Sometimes, we need to take some screenshots of the results. The tool does not provide automated features for evidence collection. We must manually modify them to place them in S3 buckets and configure them.
There could be a possibility of deploying tag-based conditions for different environments using the same code base similar to GitHub. Implementing tag-based conditions in the build spec file is possible, but the process can be simpler. They could provide this tagging functionality in the UI itself. The users could decide pipeline triggers based on the predefined rules.
The setup time is a bit long. We need a lot of experience to work with it. We need a lot of troubleshooting experience. We need to contact support if things get out of hand.
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.
AWS CodePipeline doesn't offer much room for customization.
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.
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.
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.