8 ms·

Cloud Source Repositories

83 points by cdnsteve 8y ago

tekkk 8y ago
I am intrigued by the level of sophistication this Google's private git offers. But I'm not probably in their intended audience as I'm not interested in providing my full personal and credit card information just to use git... I am probably just too ingrained in GitHub and AWS to even consider other options. But I'm curious, still. Is it ... good? I hope somebody is going to share their experience with me.
- jrs95 8y ago
  Regardless of Git you should check out Google Cloud. Massive improvement in developer experience in comparison to AWS.
- manigandham 8y ago
  It's just git so there's not much sophistication, nor is one service "better" than another in that regard. Github/Gitlab are still far more useful as they are more than just repos. The issues, PRs, wikis, and general management features are what most projects need. Azure DevOps is probably the best competitor from the clouds.
  - tekkk 8y ago
    Sure git is just git. I was referring more to the other features this PR piece is promising: Fast Code Search, Debug in production, Detailed audit logs. I am curious how they relate to say Github or other services. Also as a sidenote, the Quickstart link for Debug in production and Detailed audit logs is the same. Is it so for a purpose?
    - russellwolf 8y ago
      Cloud Source Repositories PM here. >Also as a sidenote, the Quickstart link for Debug in production and Detailed audit logs is the same. Is it so for a purpose? Thanks for pointing this out. It's not intentional. I'll make sure it gets fixed.
    - manigandham 8y ago
      Cloud Repos and Cloud Build are very lacking. I wouldn't recommend for anything other than side projects. Github, Gitlab, Azure DevOps are also either free or very cheap and have 100x more features and functionality.
- ernsheong 8y ago
  Google Cloud is worth checking out. CSR is just one of their offerings in the GCP ecosystem.
thefounder 8y ago
Well bitbucket is free regardless the number of repo so why would I choose Google repos?
- andrewbinstock 8y ago
  C'mon, man, click the link before arguing with the premise. Had you done so, you'd have seen in big bold type "Unlimited private Git repositories for free"
praseodym 8y ago
Title is wrong: they have unlimited private repositories for free, but for a maximum of 5 users per project.
- sctb 8y ago
  We dropped “5 free private repos” from the submitted title. Please, submitters, refrain from editorializing. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- lern_too_spel 8y ago
  That is also wrong. Not five users per repo but five active users per account, across all repos.
ipsum2 8y ago
Is Cloud Source Repositories using the same web app as the internal Cider tool?
- deleted 8y ago
  [deleted]
- ImJasonH 8y ago
  Nope.
client4 8y ago
And so the count down to this services death begins. /Sarcasm
shadowAuror 8y ago
For some reason, I don't trust google at all for anything...
cdoxsey 8y ago
It wasn't all that long ago that Google shut down Google Code. They said: https://opensource.googleblog.com/2015/03/farewell-to-google-code.html https://opensource.googleblog.com/2015/03/farewell-to-google... > After profiling non-abusive activity on Google Code, it has become clear to us that the service simply isn’t needed anymore. And now they've created a new product which does pretty much the same thing... Wonder how long this one will last.
- wstrange 8y ago
  AFAIK, GSR is really intended to support cloud deployment. So not a replacement for Google code. I think the assumption is that most folks will use github / gitlab , etc. as their primary, and mirror to GSR for deployment.
- ImJasonH 8y ago
  I disagree that CSR serves the same purpose as code.google.com, and is likely to meet a similar end. code.google.com hosted public repos, issues, wiki, downloads, etc., and was generally just ripe for abuse. Google created it largely because Sourceforge was the only thing that existed at the time, and it wasn't doing a great job. Today there's GitHub, Bitbucket, Gitlab, and more. CSR is primarily for hosting private code, shared among teams, and adding integrations with other Cloud services, in the Cloud Console. It also adds code search, which is pretty great. Hosting private repos, it's much less easily abused (it's not impossible). There are plenty of private repo hosts, and this one aims to be the one best integrated with GCP. It has, I think, a much better business reason to continue existing. It might not make money (I legitimately do not know) but it helps drive GCP adoption/usage, unlike code.google.com which didn't. Disclosure: I worked on code.google.com, and helped turn it down, and helped create CSR from its ashes. I don't work on either anymore.
  - gnahckire 8y ago
    > It might not make money (I legitimately do not know) but it helps drive GCP adoption/usage, unlike code.google.com which didn't. Understandable considering that AWS has codecommit and MSFT owns github now.
013a 8y ago
My biggest complaint with Google Cloud's UX, which applies to their new Cloud Source Repositories opt-in UI: They shard out so many of their user experiences into different websites and domains. Under the umbrella of Google Cloud you've got Google Cloud Console, Firebase, Stackdriver, Source Repositories, Dialog Flow, probably a couple others I'm forgetting. Almost all of these have entries on the Google Cloud Console which open a new tab and link you to a new website. It makes keeping track of where things actually are extremely difficult. For example: Firebase functions on the Firebase UI are also Google Cloud Console functions. The old Google Cloud Datastore product, which lived on the Console, is now Cloud Firestore on the Firebase console. Stackdriver logging used to be on the Stackdriver UI, now its on the Cloud Console, but there are still references to Stackdriver all over that product, and they continue to invest to Stackdriver (Istio service maps). AWS does this a little bit, in four or five of their hundreds of products. Lightsail is one example. Azure does this a little bit as well (DevOps is a separate page even though its essentially an Azure product). GCP is the worst offender. I want to see a better unifying vision for what being a Google Cloud customer actually means, instead of all these confusing and isolated experiences.
- derefr 8y ago
  > I want to see a better unifying vision for what being a Google Cloud customer actually means The thing you've got to understand is that none of these products are "Google Cloud" products. They're Google services (or, even moreso, services of random third parties which Google has acquired) that you happen to be able to hook into from your GCP project and access through the GCP CLI. The closest comparison I can think of is Heroku's "Elements", which are third-party offerings (usually of their own services, with their own service dashboards and everything!) that happen to be subscribe-to-able and high-level-configurable through Heroku's dashboard/CLI. Except, in this case, many of the third party "elements" that are subscribe-to-able and high-level-configurable in GCP, happen to be created by other departments/sub-companies of Google. Still nothing to do with GCP, though, any more than a random Heroku Element has to do with Heroku.
  - skj 8y ago
    I can tell you that your view does not match that of the engineers working on these products. If something is namespaced under a project and you use the cloud console or CLI to manage it, it is very much a GCP product. (I am one such engineer, and have worked on the CLI, cloud build, and container services)
ngcc_hk 8y ago
One day some part of not all will shutdown and disappear and where is your sources again.
atombender 8y ago
Interesting that they're going this way. We used Google's source repository functionality for a while because there is no real choice if you want to use Google Cloud Builder, which we were testing out for cloud-based Docker builds. GCB was pretty disappointing, and we moved off it. We also found the source repository service annoying. GCB can't pull code from Github, so you first have to set up a Google source repo and turn on Github sync; the source repo is, in other words, only there to be a mirror. Unfortunately, this introduces problems. You get latency -- your Google repo is always behind. Worse, we frequently experienced a situation where the sync was broken, either due to Github being flaky, or the syncing itself being flaky. In such cases, it was impossible to tell what the status of the sync was; all you could do was go into the UI and see that it was not up to date; no way to force a sync. So this setup became a liability. At the time (not sure if this is still the case), there was also no API to set up new mirrors, it was all manual. The whole UI around GCB and source repos seemed to have been created in a rush, very bare bones. A lot of Google serviced start out like this. I suppose this is a strategic play. For developers, you'd get a better UX if Google simply had tighter integration with Github and Gitlab, but Google probably doesn't want that. However, the low quality of their offerings so far (especially, cough, StackDriver) mean that this stuff will have an uphill battle in proving itself to developers, most of whom already have an allegiance to better tools like Github. If you're already on Github, why would you use this stuff?
- mrep 8y ago
  > Worse, we frequently experienced a situation where the sync was broken, either due to Github being flaky, or the syncing itself being flaky. In such cases, it was impossible to tell what the status of the sync was; all you could do was go into the UI and see that it was not up to date; no way to force a sync. Having worked for some of the big 5 American tech conglomerates, I would say this is the exact reason why they did not support it initially nor fully. The bigger the company, the more risk their is running/depending on someone else's software SLA/scaling/dependencies/security/privacy/laws... You just had a bad experience with Google cloud but you don't really know if it was google's fault or Githubs. Plus, they have so many software developers, they can build their own version that conforms to their requirements themselves for practically the same costs.
- 8y ago
faizmokhtar 8y ago
Will there be pull request support anytime soon?
- Insanity 8y ago
  I was surprised to find this is missing. I do hope they add this.
noodlesUK 8y ago
Has anyone noticed how they use what appears to be the GitHub logo on this page...? Surely that isn't okay. https://cloud.google.com/images/products/source-repositories/unlimited-private-git-repositories.svg https://cloud.google.com/images/products/source-repositories...
- warent 8y ago
  It says right underneath it "Mirror code from GitHub" There's nothing wrong with using imagery to draw your attention to related features.
  - noodlesUK 8y ago
    I'd tend to agree if it weren't listed right next to the feature "Unlimited private Git repositories for free", which is a feature GitHub charges for, but seeing as this is a somewhat competitive product, it feels a little suspect.
vira28 8y ago
I am a GCP user and we use Gitlab. I understand that CSR provides better integration with other services in GCP. However, I am achieving most of those using gitlab-ci. Can someone explain (not sure, if I am missing anything) why should I move to CSR? If not, I will better stay with gitlab. TIA.
zawerf 8y ago
Code search might be the killer feature here. I used to work at google many eons ago and I spend 90% of my day wading through billions LOCs with their internal code search tool. I believe it's the same one used by chromium: https://cs.chromium.org/ https://cs.chromium.org/
- russellwolf 8y ago
  Cloud Source Repositories PM here. It is indeed using the same code search infrastructure as the Chromium code search site as well as the Google internal code search site. You can read more about the Cloud Source Repositories code search feature in a blog post here: https://cloud.google.com/blog/products/application-development/introducing-new-cloud-source-repositories https://cloud.google.com/blog/products/application-developme...
madrox 8y ago
Without all the nice bells and whistles github provides for collaboration like wikis and issue tracking I don't think google will be successful at convincing people to maintain their code here. I don't find the outliner useful. That's a common IDE feature and a repo is not an IDE. I've always viewed source control as a productivity tool more than infrastructure. With that mindset, it will take a lot more to convince people to do more than mirror their code here. Maybe that's enough, but mirroring has its headaches...
deleted 8y ago
[deleted]
dickeytk 8y ago
tl;dr: this isn't replacing github, it's solving a more specific problem I think everyone here is missing the point. The purpose here seems to be similar to github actions in providing workflows around repository events (though also including some basic ability to view the code as well). Having a clean way to cut a release that updates app servers on app engine and serverless functions in tandem is needed right now. I don't think this is intended to be used by anyone that doesn't have their platform on GCP. For highly sensitive codebases within an organization, they may not want to host it on microsoft's servers as well—but this seems secondary to the workflow functionality. It's possible I'm incorrect though and I do think the messaging here should be improved. Chiefly that it shouldn't lead with "Unlimited private Git repositories for free"
- manigandham 8y ago
  >> Having a clean way to cut a release that updates app servers on app engine and serverless functions in tandem is needed right now. This is the entire field of CI/CD with dozens of providers, including Github and Gitlab too.
  - dickeytk 8y ago
    I'm not claiming they're the only ones (I called out github's offering explicitly). I'm just explaining why this exists because a lot of people in this thread seem to think it's a github replacement.
    - manigandham 8y ago
      I was responding to the "needed right now" part in your first comment. Unless I'm misunderstanding, do you think it's not covered by the other CI/CD providers?
      - dickeytk 8y ago
        I don't mean to imply that other products are inferior. A problem can simultaneously exist and have solutions.
Ayyar 8y ago
Xoogler here. Internally as Google, you have a substantially power powerful version of Codesearch, which is semantic, i.e. it relies on actual binary artifacts produced by builds to index code. All of the code base uses Blaze ( open sourced as Bazel) to express the rules. The version of code search here is cute, but it's still not a full blown structured semantic code search, which I really miss. Searching for and browsing code on Github feels underwhelming in comparison, because you wan't really find or explore code the way you think of it. You can see a demo of semantic Codesearch tech externalized here at: https://blog.bazel.build/2017/12/14/introducing-bazel-code-search.html#searching-the-bazel-codebase https://blog.bazel.build/2017/12/14/introducing-bazel-code-s... http://cs.chromium.org http://cs.chromium.org For example if you click on a header or a symbol, you can get proper cross references to a symbol. https://cs.chromium.org/chromium/src/pdf/document_loader_impl.cc?dr&g=0&l=43 https://cs.chromium.org/chromium/src/pdf/document_loader_imp... I really wish they add structured code search to Cloud Repos, even if it comes with some heavy restrictions such you must use Bazel as a build system. It would be a killer feature, and to my knowledge there is no equivalent to such a product. IDEs offer some similar overlapping functionality, though other code search engines still operate in terms of strings rather than actually real binary symbols ( I think Sourcegraph is trying here but that still does not seem to use some kind of accurate and structured information like you have in the code, it still seems not use build rules).
- toeenredbluo 8y ago
  How do you deal with things like system headers then? Force everyone to check in their OS (bye BSDs)? Assume everyone runs the same OS? How do you deal with compiler provided internals, where someone might be using clang which has behavior X, but gcc / icc / msvc doesn't? These problems are more prominent in C/C++, but are everywhere... Not easy... Google can probably check in everything for themselves... Probably not so easy for other companies? Maybe? Can Google solve this without sinking too much resources into it?
  - Ayyar 8y ago
    My understanding of this is the Google approach is to have all builds in the cloud using Forge i.e. infrastructure that lets you cloud builds. This means you can do hermetic builds, and thousands of other engineers can reuse the build artifacts you produce. And in the particular context of tools such as code searching, your build artifacts update the code searching index pretty quickly post committing a change.
abtinf 8y ago
I find the pricing of this service to be incomprehensible, as well as contradictory to “Unlimited private Git repositories for free”. Can anyone explain it?
- dragonwriter 8y ago
  > I find the pricing of this service to be incomprehensible, as well as contradictory to “Unlimited private Git repositories for free”. You get unlimited private repositories, 5 project users, 50 GB of storage, and 50 GB egress per monthly for free. Monthly overage charges beyond the free quota are $1 per project-user, $0.10 per GB of storage, and $0.10 per GB of egress. So for 10 project-users, 100 GB of storage, and 200 GB of egress in a month, you pay $5 for users, $5 for storage, and $10 for egress, for a total of $20.
  - abtinf 8y ago
    I still don’t get it. What is a “project” and how does it differ from a “repo”? If they are the same thing, isn’t every project/repo going to cost at least a $1?
    - russellwolf 8y ago
      Cloud Source Repositories PM here. A project as described here refers to a "Cloud Project" which is the basis for creating, enabling, and using all GCP services including managing APIs, enabling billing, grouping resources, etc. Within a project, one could have tens or hundreds of repositories. With 6 users on a single project, you would pay $1/month total (because the first 5 users are free) and all those users would have access to every repository in that project. I appreciate your feedback that you find the pricing model and project concept difficult to understand. I'll bring this back to the team and we'll look at different ways to improve this.
      - abtinf 8y ago
        Thank you - this explanation is much more clear and I understand now. I’m generally familiar with AWS but haven’t used GCP, so I didn’t have the “Cloud Project” concept.
jpatokal 8y ago
Not sure why this is trending now: this went GA back in May 2017: https://cloud.google.com/blog/products/gcp/cloud-source-repositories-now-ga-and-free-for-up-to-five-users-and-50gb-of-storage https://cloud.google.com/blog/products/gcp/cloud-source-repo... Previous HN discussion: https://news.ycombinator.com/item?id=14413035 https://news.ycombinator.com/item?id=14413035 However, Google has recently launched a raft of new CSR features, including semantic code search: https://cloud.google.com/blog/products/application-development/introducing-new-cloud-source-repositories https://cloud.google.com/blog/products/application-developme...

83 points by cdnsteve 8y ago

I am intrigued by the level of sophistication this Google's private git offers. But I'm not probably in their intended audience as I'm not interested in providing my full personal and credit card information just to use git... I am probably just too ingrained in GitHub and AWS to even consider other options. But I'm curious, still. Is it ... good? I hope somebody is going to share their experience with me.

jrs95 8y ago
Regardless of Git you should check out Google Cloud. Massive improvement in developer experience in comparison to AWS.
manigandham 8y ago
It's just git so there's not much sophistication, nor is one service "better" than another in that regard. Github/Gitlab are still far more useful as they are more than just repos. The issues, PRs, wikis, and general management features are what most projects need. Azure DevOps is probably the best competitor from the clouds.
- tekkk 8y ago
  Sure git is just git. I was referring more to the other features this PR piece is promising: Fast Code Search, Debug in production, Detailed audit logs. I am curious how they relate to say Github or other services. Also as a sidenote, the Quickstart link for Debug in production and Detailed audit logs is the same. Is it so for a purpose?
  - russellwolf 8y ago
    Cloud Source Repositories PM here. >Also as a sidenote, the Quickstart link for Debug in production and Detailed audit logs is the same. Is it so for a purpose? Thanks for pointing this out. It's not intentional. I'll make sure it gets fixed.
  - manigandham 8y ago
    Cloud Repos and Cloud Build are very lacking. I wouldn't recommend for anything other than side projects. Github, Gitlab, Azure DevOps are also either free or very cheap and have 100x more features and functionality.
ernsheong 8y ago
Google Cloud is worth checking out. CSR is just one of their offerings in the GCP ecosystem.

thefounder 8y ago

Well bitbucket is free regardless the number of repo so why would I choose Google repos?

andrewbinstock 8y ago
C'mon, man, click the link before arguing with the premise. Had you done so, you'd have seen in big bold type "Unlimited private Git repositories for free"

praseodym 8y ago

Title is wrong: they have unlimited private repositories for free, but for a maximum of 5 users per project.

sctb 8y ago
We dropped “5 free private repos” from the submitted title. Please, submitters, refrain from editorializing. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
lern_too_spel 8y ago
That is also wrong. Not five users per repo but five active users per account, across all repos.

ipsum2 8y ago

Is Cloud Source Repositories using the same web app as the internal Cider tool?

deleted 8y ago
[deleted]
ImJasonH 8y ago
Nope.

client4 8y ago

And so the count down to this services death begins. /Sarcasm

shadowAuror 8y ago

For some reason, I don't trust google at all for anything...

cdoxsey 8y ago

It wasn't all that long ago that Google shut down Google Code. They said: https://opensource.googleblog.com/2015/03/farewell-to-google-code.html https://opensource.googleblog.com/2015/03/farewell-to-google... > After profiling non-abusive activity on Google Code, it has become clear to us that the service simply isn’t needed anymore. And now they've created a new product which does pretty much the same thing... Wonder how long this one will last.

wstrange 8y ago
AFAIK, GSR is really intended to support cloud deployment. So not a replacement for Google code. I think the assumption is that most folks will use github / gitlab , etc. as their primary, and mirror to GSR for deployment.
ImJasonH 8y ago
I disagree that CSR serves the same purpose as code.google.com, and is likely to meet a similar end. code.google.com hosted public repos, issues, wiki, downloads, etc., and was generally just ripe for abuse. Google created it largely because Sourceforge was the only thing that existed at the time, and it wasn't doing a great job. Today there's GitHub, Bitbucket, Gitlab, and more. CSR is primarily for hosting private code, shared among teams, and adding integrations with other Cloud services, in the Cloud Console. It also adds code search, which is pretty great. Hosting private repos, it's much less easily abused (it's not impossible). There are plenty of private repo hosts, and this one aims to be the one best integrated with GCP. It has, I think, a much better business reason to continue existing. It might not make money (I legitimately do not know) but it helps drive GCP adoption/usage, unlike code.google.com which didn't. Disclosure: I worked on code.google.com, and helped turn it down, and helped create CSR from its ashes. I don't work on either anymore.
- gnahckire 8y ago
  > It might not make money (I legitimately do not know) but it helps drive GCP adoption/usage, unlike code.google.com which didn't. Understandable considering that AWS has codecommit and MSFT owns github now.

013a 8y ago

My biggest complaint with Google Cloud's UX, which applies to their new Cloud Source Repositories opt-in UI: They shard out so many of their user experiences into different websites and domains. Under the umbrella of Google Cloud you've got Google Cloud Console, Firebase, Stackdriver, Source Repositories, Dialog Flow, probably a couple others I'm forgetting. Almost all of these have entries on the Google Cloud Console which open a new tab and link you to a new website. It makes keeping track of where things actually are extremely difficult. For example: Firebase functions on the Firebase UI are also Google Cloud Console functions. The old Google Cloud Datastore product, which lived on the Console, is now Cloud Firestore on the Firebase console. Stackdriver logging used to be on the Stackdriver UI, now its on the Cloud Console, but there are still references to Stackdriver all over that product, and they continue to invest to Stackdriver (Istio service maps). AWS does this a little bit, in four or five of their hundreds of products. Lightsail is one example. Azure does this a little bit as well (DevOps is a separate page even though its essentially an Azure product). GCP is the worst offender. I want to see a better unifying vision for what being a Google Cloud customer actually means, instead of all these confusing and isolated experiences.

derefr 8y ago
> I want to see a better unifying vision for what being a Google Cloud customer actually means The thing you've got to understand is that none of these products are "Google Cloud" products. They're Google services (or, even moreso, services of random third parties which Google has acquired) that you happen to be able to hook into from your GCP project and access through the GCP CLI. The closest comparison I can think of is Heroku's "Elements", which are third-party offerings (usually of their own services, with their own service dashboards and everything!) that happen to be subscribe-to-able and high-level-configurable through Heroku's dashboard/CLI. Except, in this case, many of the third party "elements" that are subscribe-to-able and high-level-configurable in GCP, happen to be created by other departments/sub-companies of Google. Still nothing to do with GCP, though, any more than a random Heroku Element has to do with Heroku.
- skj 8y ago
  I can tell you that your view does not match that of the engineers working on these products. If something is namespaced under a project and you use the cloud console or CLI to manage it, it is very much a GCP product. (I am one such engineer, and have worked on the CLI, cloud build, and container services)

ngcc_hk 8y ago

One day some part of not all will shutdown and disappear and where is your sources again.

atombender 8y ago

Interesting that they're going this way. We used Google's source repository functionality for a while because there is no real choice if you want to use Google Cloud Builder, which we were testing out for cloud-based Docker builds. GCB was pretty disappointing, and we moved off it. We also found the source repository service annoying. GCB can't pull code from Github, so you first have to set up a Google source repo and turn on Github sync; the source repo is, in other words, only there to be a mirror. Unfortunately, this introduces problems. You get latency -- your Google repo is always behind. Worse, we frequently experienced a situation where the sync was broken, either due to Github being flaky, or the syncing itself being flaky. In such cases, it was impossible to tell what the status of the sync was; all you could do was go into the UI and see that it was not up to date; no way to force a sync. So this setup became a liability. At the time (not sure if this is still the case), there was also no API to set up new mirrors, it was all manual. The whole UI around GCB and source repos seemed to have been created in a rush, very bare bones. A lot of Google serviced start out like this. I suppose this is a strategic play. For developers, you'd get a better UX if Google simply had tighter integration with Github and Gitlab, but Google probably doesn't want that. However, the low quality of their offerings so far (especially, cough, StackDriver) mean that this stuff will have an uphill battle in proving itself to developers, most of whom already have an allegiance to better tools like Github. If you're already on Github, why would you use this stuff?

mrep 8y ago
> Worse, we frequently experienced a situation where the sync was broken, either due to Github being flaky, or the syncing itself being flaky. In such cases, it was impossible to tell what the status of the sync was; all you could do was go into the UI and see that it was not up to date; no way to force a sync. Having worked for some of the big 5 American tech conglomerates, I would say this is the exact reason why they did not support it initially nor fully. The bigger the company, the more risk their is running/depending on someone else's software SLA/scaling/dependencies/security/privacy/laws... You just had a bad experience with Google cloud but you don't really know if it was google's fault or Githubs. Plus, they have so many software developers, they can build their own version that conforms to their requirements themselves for practically the same costs.
8y ago

faizmokhtar 8y ago

Will there be pull request support anytime soon?

Insanity 8y ago
I was surprised to find this is missing. I do hope they add this.

noodlesUK 8y ago

Has anyone noticed how they use what appears to be the GitHub logo on this page...? Surely that isn't okay. https://cloud.google.com/images/products/source-repositories/unlimited-private-git-repositories.svg https://cloud.google.com/images/products/source-repositories...

warent 8y ago
It says right underneath it "Mirror code from GitHub" There's nothing wrong with using imagery to draw your attention to related features.
- noodlesUK 8y ago
  I'd tend to agree if it weren't listed right next to the feature "Unlimited private Git repositories for free", which is a feature GitHub charges for, but seeing as this is a somewhat competitive product, it feels a little suspect.

vira28 8y ago

I am a GCP user and we use Gitlab. I understand that CSR provides better integration with other services in GCP. However, I am achieving most of those using gitlab-ci. Can someone explain (not sure, if I am missing anything) why should I move to CSR? If not, I will better stay with gitlab. TIA.

zawerf 8y ago

Code search might be the killer feature here. I used to work at google many eons ago and I spend 90% of my day wading through billions LOCs with their internal code search tool. I believe it's the same one used by chromium: https://cs.chromium.org/ https://cs.chromium.org/

russellwolf 8y ago
Cloud Source Repositories PM here. It is indeed using the same code search infrastructure as the Chromium code search site as well as the Google internal code search site. You can read more about the Cloud Source Repositories code search feature in a blog post here: https://cloud.google.com/blog/products/application-development/introducing-new-cloud-source-repositories https://cloud.google.com/blog/products/application-developme...

madrox 8y ago

Without all the nice bells and whistles github provides for collaboration like wikis and issue tracking I don't think google will be successful at convincing people to maintain their code here. I don't find the outliner useful. That's a common IDE feature and a repo is not an IDE. I've always viewed source control as a productivity tool more than infrastructure. With that mindset, it will take a lot more to convince people to do more than mirror their code here. Maybe that's enough, but mirroring has its headaches...

deleted 8y ago

[deleted]

dickeytk 8y ago

tl;dr: this isn't replacing github, it's solving a more specific problem I think everyone here is missing the point. The purpose here seems to be similar to github actions in providing workflows around repository events (though also including some basic ability to view the code as well). Having a clean way to cut a release that updates app servers on app engine and serverless functions in tandem is needed right now. I don't think this is intended to be used by anyone that doesn't have their platform on GCP. For highly sensitive codebases within an organization, they may not want to host it on microsoft's servers as well—but this seems secondary to the workflow functionality. It's possible I'm incorrect though and I do think the messaging here should be improved. Chiefly that it shouldn't lead with "Unlimited private Git repositories for free"

manigandham 8y ago
>> Having a clean way to cut a release that updates app servers on app engine and serverless functions in tandem is needed right now. This is the entire field of CI/CD with dozens of providers, including Github and Gitlab too.
- dickeytk 8y ago
  I'm not claiming they're the only ones (I called out github's offering explicitly). I'm just explaining why this exists because a lot of people in this thread seem to think it's a github replacement.
  - manigandham 8y ago
    I was responding to the "needed right now" part in your first comment. Unless I'm misunderstanding, do you think it's not covered by the other CI/CD providers?
    - dickeytk 8y ago
      I don't mean to imply that other products are inferior. A problem can simultaneously exist and have solutions.

Ayyar 8y ago

Xoogler here. Internally as Google, you have a substantially power powerful version of Codesearch, which is semantic, i.e. it relies on actual binary artifacts produced by builds to index code. All of the code base uses Blaze ( open sourced as Bazel) to express the rules. The version of code search here is cute, but it's still not a full blown structured semantic code search, which I really miss. Searching for and browsing code on Github feels underwhelming in comparison, because you wan't really find or explore code the way you think of it. You can see a demo of semantic Codesearch tech externalized here at: https://blog.bazel.build/2017/12/14/introducing-bazel-code-search.html#searching-the-bazel-codebase https://blog.bazel.build/2017/12/14/introducing-bazel-code-s... http://cs.chromium.org http://cs.chromium.org For example if you click on a header or a symbol, you can get proper cross references to a symbol. https://cs.chromium.org/chromium/src/pdf/document_loader_impl.cc?dr&g=0&l=43 https://cs.chromium.org/chromium/src/pdf/document_loader_imp... I really wish they add structured code search to Cloud Repos, even if it comes with some heavy restrictions such you must use Bazel as a build system. It would be a killer feature, and to my knowledge there is no equivalent to such a product. IDEs offer some similar overlapping functionality, though other code search engines still operate in terms of strings rather than actually real binary symbols ( I think Sourcegraph is trying here but that still does not seem to use some kind of accurate and structured information like you have in the code, it still seems not use build rules).

toeenredbluo 8y ago
How do you deal with things like system headers then? Force everyone to check in their OS (bye BSDs)? Assume everyone runs the same OS? How do you deal with compiler provided internals, where someone might be using clang which has behavior X, but gcc / icc / msvc doesn't? These problems are more prominent in C/C++, but are everywhere... Not easy... Google can probably check in everything for themselves... Probably not so easy for other companies? Maybe? Can Google solve this without sinking too much resources into it?
- Ayyar 8y ago
  My understanding of this is the Google approach is to have all builds in the cloud using Forge i.e. infrastructure that lets you cloud builds. This means you can do hermetic builds, and thousands of other engineers can reuse the build artifacts you produce. And in the particular context of tools such as code searching, your build artifacts update the code searching index pretty quickly post committing a change.

abtinf 8y ago

I find the pricing of this service to be incomprehensible, as well as contradictory to “Unlimited private Git repositories for free”. Can anyone explain it?

dragonwriter 8y ago
> I find the pricing of this service to be incomprehensible, as well as contradictory to “Unlimited private Git repositories for free”. You get unlimited private repositories, 5 project users, 50 GB of storage, and 50 GB egress per monthly for free. Monthly overage charges beyond the free quota are $1 per project-user, $0.10 per GB of storage, and $0.10 per GB of egress. So for 10 project-users, 100 GB of storage, and 200 GB of egress in a month, you pay $5 for users, $5 for storage, and $10 for egress, for a total of $20.
- abtinf 8y ago
  I still don’t get it. What is a “project” and how does it differ from a “repo”? If they are the same thing, isn’t every project/repo going to cost at least a $1?
  - russellwolf 8y ago
    Cloud Source Repositories PM here. A project as described here refers to a "Cloud Project" which is the basis for creating, enabling, and using all GCP services including managing APIs, enabling billing, grouping resources, etc. Within a project, one could have tens or hundreds of repositories. With 6 users on a single project, you would pay $1/month total (because the first 5 users are free) and all those users would have access to every repository in that project. I appreciate your feedback that you find the pricing model and project concept difficult to understand. I'll bring this back to the team and we'll look at different ways to improve this.
    - abtinf 8y ago
      Thank you - this explanation is much more clear and I understand now. I’m generally familiar with AWS but haven’t used GCP, so I didn’t have the “Cloud Project” concept.

jpatokal 8y ago

Not sure why this is trending now: this went GA back in May 2017: https://cloud.google.com/blog/products/gcp/cloud-source-repositories-now-ga-and-free-for-up-to-five-users-and-50gb-of-storage https://cloud.google.com/blog/products/gcp/cloud-source-repo... Previous HN discussion: https://news.ycombinator.com/item?id=14413035 https://news.ycombinator.com/item?id=14413035 However, Google has recently launched a raft of new CSR features, including semantic code search: https://cloud.google.com/blog/products/application-development/introducing-new-cloud-source-repositories https://cloud.google.com/blog/products/application-developme...