Serverless git integration rollback
Hi team! I've recently switched over to runpod serverless for production with the git integration.
I have a concern about reliability in a failure scenario.
Firstly, I notice that the builds take roughly 1.5 hours to build out and then for a worker to download + extract the image. Consider a bad release that starts getting rolled out - I can't see a button to stop it.
Now, say it rolled out because I missed the process for whatever reason - I can't see a button to roll back to the previous good version.
The only way I currently see to roll back is to accept 1.5 hours of downtime and revert the git commit, wait for everything to build, upload, download, extract.
Is there a workaround in this sort of scenario or are you working on implementing something?
Thanks
Kristo
I have a concern about reliability in a failure scenario.
Firstly, I notice that the builds take roughly 1.5 hours to build out and then for a worker to download + extract the image. Consider a bad release that starts getting rolled out - I can't see a button to stop it.
Now, say it rolled out because I missed the process for whatever reason - I can't see a button to roll back to the previous good version.
The only way I currently see to roll back is to accept 1.5 hours of downtime and revert the git commit, wait for everything to build, upload, download, extract.
Is there a workaround in this sort of scenario or are you working on implementing something?
Thanks
Kristo
