Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cloud Source Repositories

cloud.google.com

Post reply on HN
Print view View original

61–70 of 74 posts

Re: Cloud Source Repositories

#61

Post by manigandham »

derefr wrote: post #17
013a wrote: post #14

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 Consol…

> 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…

That's not quite right. Google Cloud is basically everything, including the Google Cloud Platform (cloud computing), G-Suite, Maps, Chrome, Android, etc.

Firebase and Stackdriver are underneath GCP.

Re: Cloud Source Repositories

#62

Post by manigandham »

tekkk wrote: post #18
manigandham wrote: post #7

Earlier quoted context omitted.

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.

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?

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.

Re: Cloud Source Repositories

#63

Post by thrower123 »

dickeytk wrote: post #38

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.…

Ah, so it's Google's Visual Studio Online/VSTS/Azure DevOps[1]

[1] Microsoft name shuffling is so much fun...

Re: Cloud Source Repositories

#64

Post by jpatokal »

Not sure why this is trending now: this went GA back in May 2017: https://cloud.google.com/blog/products/gcp/cloud-source-repo...

Previous HN discussion: 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-developme...

Re: Cloud Source Repositories

#65

Post by russellwolf »

abtinf wrote: post #60
dragonwriter wrote: post #58

Earlier quoted context omitted.

> 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, an…

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?

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.

Re: Cloud Source Repositories

#66

Post by jpatokal »

abtinf wrote: post #60
dragonwriter wrote: post #58

Earlier quoted context omitted.

> 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, an…

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?

Projects are the fundamental organization unit of GCP. Every resource you create in GCP lives in a project, and users are granted access to projects.

https://cloud.google.com/resource-manager/docs/creating-mana...

"Project-user" here means that access is counted per project. So if you (x@) use GCR for projects A and B, meaning you check in/out code as x@A and x@B, that's two "project-users".

Disclaimer: I work for GCP.

Re: Cloud Source Repositories

#67

Post by abtinf »

russellwolf wrote: post #65
abtinf wrote: post #60

Earlier quoted context omitted.

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?

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 woul…

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.

Re: Cloud Source Repositories

#68

Post by dragonwriter »

atombender wrote: post #37
russellwolf wrote: post #32

Earlier quoted context omitted.

Cloud Source Repositories PM here. I appreciate your feedback and will share it with the team. >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. We've heard this was a problem for users so we're adding the ability to force a sync and to view the current sync status. These features will be live in the next few wee…

I would strongly advise you to make the mirroring system completely hidden. It's weird to me that the UI even exposes this. First, have people register their origin repos. In fact, don't let people register individual repos; just their accounts or organizations. So instead of "Source Repositories", it's just a list of repos that GCP has access to. Then, behind the scenes, mirror everything you have access to. All pro…

> Consider the developer's perspective. I already have my code on GH.

What if you don't? The fact that Google needs to acknowledge that CSR isn't where existing projects are primarily hosted (and thus needs to accommodate projects primarily hosted elsewhere) doesn't mean they shouldn't try to be a primary host.

Re: Cloud Source Repositories

#69

Post by atombender »

dragonwriter wrote: post #68
atombender wrote: post #37

Earlier quoted context omitted.

I would strongly advise you to make the mirroring system completely hidden. It's weird to me that the UI even exposes this. First, have people register their origin repos. In fact, don't let people register individual repos; just their accounts or organizations. So instead of "Source Repositories", it's just a list of repos that GCP has access to. Then, behind the scenes, mirror everything you have access to. All pro…

> Consider the developer's perspective. I already have my code on GH. What if you don't ? The fact that Google needs to acknowledge that CSR isn't where existing projects are primarily hosted (and thus needs to accommodate projects primarily hosted elsewhere) doesn't mean they shouldn't try to be a primary host.

That's fine. I'm only talking about that particular requirement that you use SR/CSR in order to use services like GCB.

Obviously you have to point GCB at something. Today, you can only point GCB at SR/CSR. If you go to GCB and try to add a trigger, and select Github, it will go and set up a mirror on SR/CSR for you.

Re: Cloud Source Repositories

#70

Post by Ayyar »

toeenredbluo wrote: post #49
Ayyar wrote: post #46

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 br…

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 no…

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.

Post reply on HN