Mastodawn

AWS Makes Kubernetes Conversational AWS finally hit Ctrl-Z on the CodeCommit deprecation, thanks to user complaints. It's back to GA (with some caveats for 2026). We break down the new timeline and why AWS is finally letting you log in like a normal human. #thecloudpod #codecommit #backfromthedead https://www.thecloudpod.net/?p=21316

The Cloud Pod Dec 19

Show thread

ferricoxide Dec 16

@kolaente @pluralistic

Honestly, my company has shit spread out across Git service-providers (#GitHub, #GitLab, #CodeCommit & #CodeBuild, etc.).

We'd switched to GitHub Actions because ones we'd previously used (e.g., #TravisCI) went from being free to being for pay …and there were still free alternatives (that, bonus, worked more-reliably).

This is just going to push more people towards running self-hosted GitLab with self-hosted runners.

Qiita - 人気の記事 Nov 29

【AWS】DevTools布教活動CodeCommit編【アドカレ2025】
https://qiita.com/Nana_777/items/a8be2eee9ee9d81326cb?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #Git #AWS #DevTools #CodeCommit #TopEngineers

【AWS】DevTools布教活動CodeCommit編【アドカレ2025】 - Qiita

はじめにこの記事は Japan AWS Top Engineers Advent Calendar 2025 の1日目の記事です。 2025年はTopEngineerに選出されましたが、その前にDevTools領域でCommunityBuilderに選出されたこともあり...

Qiita

David Nov 24

#aws #codecommit is back.

The decision was wrong. Happy that this was revised.

https://aws.amazon.com/blogs/devops/aws-codecommit-returns-to-general-availability/

The Future of AWS CodeCommit | Amazon Web Services

Back in July 2024, we announced plans to de-emphasize AWS CodeCommit based on adoption patterns and our assessment of customer needs. We never stopped looking at the data or listening to you, and what you’ve shown us is clear: you need an AWS-managed solution for your code repositories. Based on this feedback, CodeCommit is returning […]

Amazon Web Services

Ænðr E. Feldstraw Aug 29

#protip for those of you who use #AWS #CodeCommit for a #CICD repository, and pipe build artifacts to an S3 bucket: turn off versioning of the bucket objects. The pipeline won't update only changed objects: it will load all objects into the S3 bucket. That causes absolutely massive amounts of object versions, even if the number of files is small. And removing them afterwards is a pain.