Windows Desktop OS or Server OS is good for Jenkins master
LnT
Dirk Heinrichs
From: jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com]
On Behalf Of LnT
> Is Windows Desktop OS VM good or Server OS VM is good for Jenkins installation ?
No, none of them. Despite the "Server" part in the name even Windows Server isn't a (good) server OS (file locks, desktop popups, slow filesystem, etc). We've just migrated away from a Windows based Jenkins master to a Linux based one a few months ago and all those problems are gone now. Do yourself a favour and avoid Windows if you can...
Just my 2 cents.
Bye...
Dirk
--
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
jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/cafbd95e-fa7b-431c-a8be-893c0cd861c5%40googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
LnT
John.P...@nikon.com
We use ServerOS. We have four running systems worldwide so far. Server 2012 and 2016 with no server related issues on any. I don’t know any reason that Server would be required however for any of the below…
All are now running Windows Server as VM’s on ESXi 6.5 Hosts.
ESXi 6.5 Host
Windows Server 2012/16
vCenter (if ESXi fails to start you can bypass vCenter anyway, so it being hosted on the machine it admins is not an issue)
Jenkins
Windows Server 2012/16
Visual SVN
Windows Server 2012/16
VS 2012/15/17 Build servers (running Cruise Control, but talking about switching to Jenkins)
|
John E. Peterson ASW Quality Program Manager |
Nikon Metrology, Inc. |
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/46d2b582-b0c6-41a3-a744-3b4b91db1263%40googlegroups.com.
Simon Richter
On 16.04.2018 12:03, LnT wrote:
> Actually we will be providing Windows VMs. Not Linux.
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