To be able to restart the server (e.g. to deploy a new plugin version, increase heap memory or whatever) without losing the current build requests it would be nice to
1. only finish running builds (not the waiting ones)
2. persist the build requests in the queue
3. shut down the server
on start of the server:
1. load build requests
2. start builds
Description
To be able to restart the server (e.g. to deploy a new plugin version, increase heap memory or whatever) without losing the current build requests it would be nice to
1. only finish running builds (not the waiting ones)
2. persist the build requests in the queue
3. shut down the server
on start of the server:
1. load build requests
2. start builds
Also upgrading the server would be much easier if we can do that without losing build requests. Now we have to pause the system on e.g. 00:00 to be able to upgrade in the morning.
We have also some exotic build machines where builds take a long duration and that makes it impossible to just say we pause the system 1 hour before the upgrade.
AlSt[26/May/14 09:35 AM]
Also upgrading the server would be much easier if we can do that without losing build requests. Now we have to pause the system on e.g. 00:00 to be able to upgrade in the morning.
We have also some exotic build machines where builds take a long duration and that makes it impossible to just say we pause the system 1 hour before the upgrade.
We have also some exotic build machines where builds take a long duration and that makes it impossible to just say we pause the system 1 hour before the upgrade.