Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing GitLab CI vs Google Cloud Source Repositories, the Slant community recommends GitLab CI for most people. In the question“What are the best hosted version control services?” GitLab CI is ranked 7th while Google Cloud Source Repositories is ranked 8th. The most important reason people chose GitLab CI is:
All build setup are stored in .gitlab-ci.yml file, which is versioned and stored in the project. Like Travis do.
Specs
Question Ranking
Pros
Pro File based configuration
All build setup are stored in .gitlab-ci.yml file, which is versioned and stored in the project. Like Travis do.
Pro Free and open source
All of GitLab CI's code is open source and under the MIT license.
Pro Parallel builds lessen test times
Tests are parallelized across multiple machines in order to reduce test times considerably.
Pro Docker intergration
Good integration with Docker.
Pro Highly scalable
The tests of GitLab CI run parallel to each other and are distributed on different machines. Developers can add as many machines as they want or need, making GitLab CI highly scalable to the development team's needs.
Pro Quick setup for projects hosted on GitLab
Since it uses the GitLab API for setting up hooks, the setup of GitLab CI for projects hosted on GitLab can be done in one click.
Pro Kubernetes integration
Easy to test and deploy on Kubernetes.
Pro Free tier
Cloud Source Repositories is free for up to 5 project-users per billing account. The free tier comes with up to 50GB free storage total and 50GB free egress per month.
Pro Excellent security
Everything is stored encrypted in Google's datacenters. You can give fine grained control to other Google accounts and collaborate.
Pro Integrated with other Google Cloud Platform services
Trigger deployments or create custom integrations using Google Cloud Pub/Sub, deploy directly to App Engine or Cloud Functions, and use Cloud Build for CI. Check out code securely (Service Accounts) from your Cloud Compute instances or Container Engine images. View logs in Stackdriver.
Cons
Con Not lightweight
Not a lightweight solution, demanding and memory hungry.
Con Cost
Larger projects will need upgraded version
Con Security risks
Con Windows not supported
No Windows support, but it's possible to use a Bitnami stack.
Con No inline editing
Unlike some other popular repositories, there is no way to edit inline directly from the source browser. Although, you can easily open up a Theia-based IDE in the browser to edit and run your code by clicking the "Open in Cloud Shell" button. You will still have to commit your changes from the Cloud Shell command line, though.
Con Markdown styling is not as good as GitHub or GitLab
Your README files will not render as nicely as GitHub and GitLab, which may irritate you if you're migrating your repos with nicely-formatted docs.
Con Must set-up billing account
For all Google Cloud Platform projects you must enable Billing. This isn't uncommon for cloud hosting providers but it still could be considered a CON.
