2021-08-18T16:05:27Z

What needs improvement with AWS CodePipeline?

Miriam Tover - PeerSpot reviewer
  • 0
  • 25
PeerSpot user
8

8 Answers

Udhay Prakash Pethakamsetty - PeerSpot reviewer
Real User
Top 5
2024-02-23T16:13:53Z
Feb 23, 2024

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.

Search for a product comparison
Phanindra Sangers - PeerSpot reviewer
Real User
Top 5Leaderboard
2024-01-24T14:21:34Z
Jan 24, 2024

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.

Bertin Fonge - PeerSpot reviewer
Real User
Top 5Leaderboard
2023-10-25T09:30:23Z
Oct 25, 2023

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.

Miguel Aedo - PeerSpot reviewer
Real User
Top 20
2023-10-03T21:36:28Z
Oct 3, 2023

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.

Peng Zhi - PeerSpot reviewer
Real User
Top 10
2023-06-30T09:09:54Z
Jun 30, 2023

AWS CodePipeline doesn't offer much room for customization.

Isuru Jayathissa - PeerSpot reviewer
Real User
Top 5
2023-01-31T16:02:49Z
Jan 31, 2023

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.

Find out what your peers are saying about Amazon Web Services (AWS), GitLab, Jenkins and others in Build Automation. Updated: March 2024.
765,386 professionals have used our research since 2012.
MOMEN ABDELSADEK - PeerSpot reviewer
Real User
Top 5Leaderboard
2023-01-06T17:02:42Z
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.

VM
Real User
2021-08-18T16:05:27Z
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.

Build Automation
Build automation tools automate the time-consuming tasks inherent in creating a “build,” or usable version of an application. They automate and orchestrate the sometimes complex processes of compiling computer source code into binary code and packaging that binary code as well as running automated tests Some PeerSpot members use build automation solutions. In reviews, they offer opinions on the most significant selection factors to consider when looking at this type of software. One theme...
Download Build Automation ReportRead more