$\"screenshot$

How to delete a CodeCommit repository — after migrating to another service (AWS)<\/p><\/div>\n

“After migration, you have the option to continue to use your current AWS CodeCommit repository, but doing so will likely require a regular sync operation between AWS CodeCommit and the new repository provider,” the cloud giant provider advised.<\/p>\n

Market Impact of CodeCommit<\/h2>\n
Launched in 2015<\/a>, AWS CodeCommit provided a managed revision control service to host git repositories<\/a>. It was designed to work with Git-based tools as well as with other AWS tools such as the CloudGuru code analysis software<\/a>.<\/p>\n
Nonetheless, the service had trouble gaining a foothold in the competitive code repository market, despite the natural appeal for AWS shops to stick with AWS for additional services.<\/p>\n
TNS Analyst Lawrence Hecht<\/a> noted that, in last year’s JetBrains survey<\/a>, 3.2% of the developers surveyed used CodeCommit. Even among developers whose company primarily uses AWS for the cloud, only 9% used AWS CodeCommit.<\/p>\n
Those same AWS-centric accounts were much more likely to say their company was using BitBucket<\/a> (39%), GitLab<\/a> (45%) and GitHub<\/a> (63%)<\/p>\n
“That is not a large user base, but it will be interesting to see where those people will migrate to,” noted Hecht in a Slack message.<\/p>\n