5 ms·

Wow genuinely surprised that AWS is not using CodeCommit

• withhighprod 8y ago
  It’s just product and amazon didn’t even dogfood internal with it. The internal tools I heard was the best years ago until google hired the original amazon tooling people and so google is the best now
• guitarbill 8y ago
  Have you used it? Maybe you'd be less surprised :D If you want open source contributions, AWS' Code* offerings are a terrible choice. For example, AFAIK you still can't display a build status page that people can view without being logged into the AWS console, like Travis CI or AppVeyor. I honestly don't know who they built those services for, but I'll take Travis CI or Jenkins over those services any day.
  • rrix2 8y ago
    > I honestly don't know who they built those services for, but I'll take Travis CI or Jenkins over those services any day. People who aren't developing open source software and people who want integrated IAM, generally. Git repos having ARNs is pretty neat
    • guitarbill 8y ago
      You can use Jenkins for closed source. And if you've found a way to display HTML reports (unit tests, coverage, etc) using CodePipeline and IAM but without a hacky Lambda to proxy it from S3 with auth, I'd also love to know. But as is, I believe the offerings are inferior to open source tooling, and don't promote code quality.
  • rhacker 8y ago
    I have and yes, I'm not surprised :P Similar experience for other build tools tied to IAM. It's not that IAM is bad or anything, but there's always some convoluted way to get git or docker or kubernetes working when it's tied to AWS.