You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The experience of the button is amazing: click, get something running.
But that's how you should deploy software. That's great for demos or for one-shot images that don't have to be updated, but not great for iterating on a codebase. Consequently, this limits the use cases for the button (we should not use the button for "boilerplate"-type repositories)
A more sustainable way for customers to go from GitHub to Cloud Run would be:
Fork the repo.
set up a Cloud Build Trigger to automatically deploy from the fork to Cloud Run
Setting up GCB is harder than you think if not impossible. Right now you can't just set up GitHub <=> GCB integration via the API. I filed a feature request for it several years ago, but there's no plan to do it.
Cloud Run Button is great for the optional initial provisioning and first deployment
gcloud builds submit --tag/gcloud run deploy is okay for a two-step re-deployment
gcloud builds submit with a configured cloudbuild.yaml is great for re-deployment
Firing that GCB call through a trigger is good for continuous deployment
It'd be neat if the button could show a cloudbuild.yaml re-deployment equiv example. If that's just a basic generic file, or if it's generated from the app.json, either way.
The authentication required to link GH and GCB limits the flow of the automation of the full CD process.
The experience of the button is amazing: click, get something running.
But that's how you should deploy software. That's great for demos or for one-shot images that don't have to be updated, but not great for iterating on a codebase. Consequently, this limits the use cases for the button (we should not use the button for "boilerplate"-type repositories)
A more sustainable way for customers to go from GitHub to Cloud Run would be:
Maybe the button could help do that?
This would address along the way:
The text was updated successfully, but these errors were encountered: