Cloud Run Button: Click-to-deploy your Git repos to GCP

Re:Cloud Run Button: Click-to-deploy your Git repos to GCP by leetrout on Wednesday August 21, 2019 @01:26PM (#20759287)

That is fascinating. It's one of those "feels so obvious" type of things. I wonder how hard it will be to track versions of things?

I guess the "safest" workflow would be to fork the repo before you click run but the article doesn't say how to handles repeat clicks... multiple environments or if it prompts you? Off to test!

[ Parent | on HN ]

Re:Cloud Run Button: Click-to-deploy your Git repos to GCP by sansnomme on Wednesday August 21, 2019 @02:20PM (#20759923)

They had this in Heroku for years, just that it wasn't cheap.

https://elements.heroku.com/buttons

[ Parent | on HN ]

Re:Cloud Run Button: Click-to-deploy your Git repos to GCP by leetrout on Wednesday August 21, 2019 @01:50PM (#20759527)

To save anyone else some time if they stumble across my comment... It creates multiple revisions, even from distinct forks, based on what appears to be the repo name (cloud-run-hello).

First run from a fork:

This created the revision "cloud-run-hello-00001" of the Cloud Run service "cloud-run-hello"...

After changing the button's HTML to point to my repo on my fork:

This created the revision "cloud-run-hello-00002" of the Cloud Run service "cloud-run-hello"...

[ Parent | on HN ]

Re:Cloud Run Button: Click-to-deploy your Git repos to GCP by badrequest on Wednesday August 21, 2019 @05:39PM (#20762129)

Cloud Run requires a deployed container image somewhere. That can be Docker Hub or GCR, but the image version is what it actually operates on.

[ Parent | on HN ]