10 months ago
- I change env vars. 8 deployments initialize.
- I push code. 8 more deployments initialize.
- I don't need initial 8 deployments. I don't care about them.
- I manually go through each service to remove or abort the initial 8 deployments.
Is there a setting where I can auto abort or remove outdated (code) deployments?
5 Replies
10 months ago
Hey there! We've found the following might help you get unblocked faster:
- 🧵 Github auto deployments not working
- 🧵 Persistent content caching despite successful deployments
- 🧵 New Deployments taking a long time.
If you find the answer from one of these, please let us know by solving the thread!
10 months ago
Hello,
This is news to me. Can you walk me through how you are changing variables to cause eight separate deploys?
Status changed to Awaiting User Response Railway • 11 months ago
10 months ago
Shared variable change which applies to 8 different machines.
Status changed to Awaiting Railway Response Railway • 11 months ago
10 months ago
I think I know what you mean. You don't want the variable change to trigger deploys, since the deploys are going to happen anyway when you push code. Do I have that correct?
If so, when making your variable changes, use the keyboard shortcut Alt + Shift + Enter to save the changes without triggering any deployments.
Status changed to Awaiting User Response Railway • 11 months ago
10 months ago
Ah ok. Good to know. That should do it. Thanks
Status changed to Awaiting Railway Response Railway • 11 months ago
Status changed to Solved 59023g • 11 months ago