Schedule Updates for a given GitLab Hosted instance

Per Lucas Klein, "It would be great if we could set a timeframe for auto-upgrades, though (e.g. 'between 11pm-12am GMT')"

Hey there! Thanks for opening the issue, Connor.

Sometimes the GitLab upgrade causes downtime which disrupts our workflow quite badly (can't deploy hotfixes and worse). So I have disabled the auto-upgrade, leaving our instance vulnerable if I don't remember to upgrade regularly. When I perform an upgrade, I usually schedule it to "nighttime" when hopefully nobody is using it. It would be awesome if we could reactivate the auto-upgrade (so we don't have to remember to upgrade manually) but set a timeframe in which the upgrade shall be performed.

Hi @lukasklein The upgrades are currently scheduled for 11:00 pm for the local server time. This means if your instance is in New York data center it will be upgraded at 11:00 pm EST.

In recent times there were some issues with backups and upgrades fighting and so an upgrade might fail and keep trying into later parts of the day. This is no longer happening. Maybe the issue is addressed now?

Hi @dblessing, that sounds like a great default (and is sufficient for my case)! I didn't know about this, maybe you should put that into a help text next to the switch.

To be honest I have never tried the autoupdate feature on GitHost.io simply because I did not know about its behaviour. Our developers just asked me to turn it off since we had severe productivity issues before on GitLab.com when it was running an upgrade during our work-time that sometimes caused the service to be down for an hour.