Google is integrating projects deployed and running on their cloud infrastructure with a Git-based repository called Cloud Source Repository.
Google announced the termination of their Project Hosting service available on Google Code in March, providing tools for migrating the code to other source code repositories such as GitHub and Bitbucket. But about the same time, they launched the Cloud Source Repository (CSR) service in beta, without making a formal announcement. While this may seem confusing at the first sight, it turns out that CSR is not a replacement for Google Code, and not a competitor for GitHub and Bitbucket.
Cloud Source Repository is a Git service for projects deployed and run on Google’s cloud infrastructure. The code repositories are private, encrypted and replicated across multiple data centers for safety and backup purposes. A CSR can be created as a remote for a local Git repository or by connecting to GitHub or Bitbucket and importing one from there. CSR comes with basic functionality accessible from the Developer Console: a repository browser, a commit history tracker, a modified files viewer showing the differences between different versions and a simple file editor.
Currently, CSR does not offer the option to create or delete new files from the console. Such operation are to be performed on the local repository or the GitHub/Bitbucket one and changes are automatically synchronized with the cloud.
Google has integrated CSR with their Cloud Debugger which currently supports only Java code deployed on App Engine or Compute Engine. The debugger allows setting up conditional breakpoints, creating watches, inspecting local variables and the call stack, and taking snapshots.
Google Cloud Source Repository is free while in beta and stores repositories up to 500MB in total.
Amazon announced a similar service called CodeCommit during re:Invent 2014, meant to provide integrated hosting for Git projects running on AWS. CodePipeline, a complementary service, is meant to provide continuous delivery and release automation. Although they were supposed to be made available in early 2015, the services are still not public.