Try our new research platform with insights from 80,000+ expert users

Share your experience using Canonical Bazaar

The easiest route - we'll conduct a 15 minute phone interview and write up the review for you.

Use our online form to submit your review. It's quick and you can post anonymously.

Your review helps others learn about this solution
The PeerSpot community is built upon trust and sharing with peers.
It's good for your career
In today's digital world, your review shows you have valuable expertise.
You can influence the market
Vendors read their reviews and make improvements based on your feedback.
Examples of the 99,000+ reviews on PeerSpot:

Andrea-Carella - PeerSpot reviewer
DevOps Engineer at GFT Group
MSP
Top 5Leaderboard
Has improved repository management through policy customization but needs better integration with external tools
Pros and Cons
  • "It is a really good product where you can easily create your repository and integrate it with other tools such as IAM to handle the user and management aspects of the repository."
  • "The number of users for AWS CodeCommit is generally less compared to other version control systems."

What is our primary use case?

AWS CodeCommit is a version control system integrated directly in the cloud environment, similar to GitHub, GitLab, and other platforms. It offers every single benefit of using any other version control system.

What is most valuable?

AWS CodeCommit was used as a version control system in an AWS environment. The IAM integration was utilized to set the correct permissions for users in order to edit the repository, write on the repository, and view the repository. It is a really good product where you can easily create your repository and integrate it with other tools such as IAM to handle the user and management aspects of the repository.

You can easily set branch strategies and define branch rules without much difficulty or errors. You can also limit pushes and merges by setting rules to define who can approve and handle all approval-related tasks. AWS CodeCommit is really integrated with IAM, allowing you to use IAM rules and IAM policies to set specific requirements and policies for groups, including policies for committing, editing code, and viewing code.

Encryption capability was potentially used to store secrets and values that were in use with the pipeline and the code that triggered pipelines, though the specific details of this usage are not entirely certain. AWS CodeCommit is a good product for handling all tasks related to version control systems and managing the branch strategy of your repository. Compared to other tools outside AWS such as GitHub, GitLab, or Bitbucket, you can customize the policies of your users better with IAM policies in AWS CodeCommit.

What needs improvement?

AWS CodeCommit is a good product to use when you also have to use CodePipeline because it is all integrated in the same system, which is beneficial. However, the integration with other code pipeline tools outside the AWS world is uncertain, as there has been no experience with that integration.

The number of users for AWS CodeCommit is generally less compared to other version control systems. To improve the adoption of AWS CodeCommit with respect to others that are more used in the market, something would need to be done to increase market share, as people are often more educated to use GitLab or GitHub. AWS CodeCommit is quite easy to learn in general, but competitors have a bigger market share in this particular area for many reasons.

For how long have I used the solution?

AWS CodeCommit has been used for approximately one year.

What do I think about the stability of the solution?

AWS CodeCommit is stable.

What do I think about the scalability of the solution?

The scalability of AWS CodeCommit is uncertain due to not having a chance to test it, though it appears to be quite scalable.

How are customer service and support?

Support for AWS CodeCommit has never been reached, so there is no information about customer service.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

No previous solutions were used before AWS CodeCommit.

How was the initial setup?

AWS CodeCommit was not installed through AWS Marketplace. It was already installed and provided as part of the existing infrastructure by the team.

What other advice do I have?

Automated notification within the AWS CodeCommit pipeline or repository was never used. Notifications were not sent to users, as accounts were simply created. Notifications might be used when you do a pull request to notify the other reviewer to review the pull request, or when you have to approve something, to send notification to the approval team. The overall review rating for this product is seven out of ten.

Which deployment model are you using for this solution?

On-premises

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: My company has a business relationship with this vendor other than being a customer. Integrator
Flag as inappropriate
reviewer2618670 - PeerSpot reviewer
AWS & Azure Engineer at a media company with 11-50 employees
Real User
Top 5Leaderboard
Implementation of complex branch strategies enhances development workflow and reduces deployment times
Pros and Cons
  • "Applying GitHub Actions saves so much time for the team because it automates the developer's work to the server."
  • "Applying GitHub Actions saves so much time for the team because it automates the developer's work to the server."
  • "If we have complex branch strategies, it becomes very complicated to manage all those branches."
  • "If we have complex branch strategies, it becomes very complicated to manage all those branches."

What is our primary use case?

I use GitHub for its repository, and I have also used it for GitHub CI/CD pipeline or GitHub Actions.

I have integrated GitHub with AWS Elastic Beanstalk service for code purposes and also in Azure App Service. After implementation, it is very easy to get code, and we do not need to use any cloud-related repository tools for code storage. So it is very easy.

I only used GitHub enterprise; otherwise, I mostly use the open-source version.

What is most valuable?

The best feature of GitHub is its branch techniques, and it is very useful for how the branches are managed. This is the best feature I prefer.

Applying GitHub Actions saves so much time for the team because it automates the developer's work to the server.

When working with the CI/CD pipeline and somebody is writing the workflow file, it would be best to include the AI feature so if they write incorrect code, it will notify me about it in the same dashboard, eliminating the need to use third-party tools to review the file.

I use GitHub as it is easy to get code, and we do not need any cloud-related repository tools for code storage.

What needs improvement?

When working with the CI/CD pipeline and somebody is writing the workflow file, it would be best to include the AI feature so if they write incorrect code, it will notify me about it in the same dashboard, eliminating the need to use third-party tools to review the file. I would like to implement the AI feature, especially in the workflow file.

For how long have I used the solution?

I have extensively been working on GitHub for the past two years, and my total experience is about five years.

What was my experience with deployment of the solution?

The initial setup of GitHub is very easy and not complicated at all. Especially when we apply it to the CI/CD pipeline as an open-source solution, it is very easy to implement.

What do I think about the stability of the solution?

GitHub is very stable for me with no performance issues.

What do I think about the scalability of the solution?

GitHub is very scalable.

How are customer service and support?

I have not used customer support for GitHub.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

I was first introduced to GitHub, so I did not use any other solutions for coding purposes because GitHub was my first encounter.

How was the initial setup?

The initial setup of GitHub is very easy and not complicated at all. Especially when we apply it to the CI/CD pipeline as an open-source solution, it is very easy to implement.

What about the implementation team?

If you are new, especially for developers, it is very easy for the first implementation and pushing the code.

What was our ROI?

I would rate GitHub nine out of ten because if we have complex branch strategies, it becomes very complicated to manage all those branches.

What's my experience with pricing, setup cost, and licensing?

GitHub is very stable for me with no performance issues.

Which other solutions did I evaluate?

I have not used customer support for GitHub.

What other advice do I have?

I only use GitHub; I have not worked with any other version control systems or products of the same kind.

I have not used GitHub security alerts.

I also have not used GitHub API for automating workflows in my projects.

I am not utilizing code review capabilities in GitHub.

I rate GitHub 9 out of 10.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Flag as inappropriate