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

11–20 of 74 posts

Re: Cloud Source Repositories

#12

Post by cdoxsey »

It wasn't all that long ago that Google shut down Google Code. They said: 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.

Re: Cloud Source Repositories

#14

Post by 013a »

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.

Re: Cloud Source Repositories

#15

Post by wstrange »

cdoxsey wrote: post #12

It wasn't all that long ago that Google shut down Google Code. They said: 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.

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.

Re: Cloud Source Repositories

#17

Post by derefr »

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

Re: Cloud Source Repositories

#18

Post by tekkk »

manigandham wrote: post #7
tekkk wrote: post #2

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.

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?

Re: Cloud Source Repositories

#19

Post by ImJasonH »

cdoxsey wrote: post #12

It wasn't all that long ago that Google shut down Google Code. They said: 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.

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.

Post reply on HN