Hi, On 16.04.2018 12:03, LnT wrote:
> Actually we will be providing Windows VMs. Not Linux. > Hence looking for a piece of advice. - *Desktop OS or ServerOS ?* Desktop forces a reboot to install updates, which is not coordinated with running services. Jenkins really doesn't handle shutdowns well if you didn't make sure beforehand that no builds are running. Expect spurious build failures, builds missing from the list and incomplete artifact archives. Server allows you to run updates manually, but someone needs to do that and synchronize it with Jenkins, which is administration effort for either you or your customers. This should be scriptable most likely, so not all hope is lost. If you really want to provide a turnkey solution, I hate to say it, but Docker is the best idea, because it allows you to prepare an updated base system image or Jenkins installation without affecting the running instances, then you schedule a shutdown inside Jenkins and restart with minimal downtime. I'm not sure how far along Docker on Windows is these days though. MS sells it as a solution so it's probably not all bad, but I know no one actually using it. Simon -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/656bb959-438c-fb0d-ef92-a99412845552%40hogyros.de. For more options, visit https://groups.google.com/d/optout.
