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
Im actually looking for inputs on how to kill the builds. The way I thought of it is to have an api DELETE /builds/1234 or so, but then there is no reliable way to really kill a build, I can only stop it at various checkpoints. Maybe that's already enough?
For queueing pushes I would suggest to try to push once and retry, only once, after 2 mins if the first push fails. The problem here is that it'd still be wonky.
Im just a bit worried that introducing a queue system would make things more complicated -- maybe im just overthinking.
If we have a queue I could save the build as built-locally and then have a background process that watches for built-locally builds and push them one by one. Then the main build process would poll for the buils status and see that it changes to pushed and go ahead with the rest of the build flow ie. notifications etc etc. What do you think?
what are your thoughts about the ability to kill a running build?
how about queueing pushes/builds of the same project to prevent the failing builds?
The text was updated successfully, but these errors were encountered: