Recommendations for updating the build server

Question

As a guy who often switches between QA, build, and operations, I always run into the problem of what to do with operating system updates on the build server. The dichotomy is the same on Windows, Linux, MacOS, or any other o / s that can update itself via the Internet:

• The QA team wants to keep the build server exactly the same as it does from the very beginning of the product release cycle to the end, because installing updates can destabilize the server and means that consecutive builds are not performed on the same baseline.
• The ops team wants the software to be deployed on the system with all the latest security fixes; this may mean that the software is not deployed on the same version of o / s on which it was built.

I usually reduce this by taking release candidate builds and installing them on a test server that has fully updated o / s, repeating the automatic tests that run on the build server, and doing some additional system-level testing so that everything is okay before deployment. However, this seems to me ineffective; Does anyone have a better way?

Answer 1

, - . , :

• , , , . .. Windows , interweb. , WPF/Silverlight ASP.Net, Winforms, - , WinAPI , .

• - , - IOW, , xyz, - ,

• QA ,

• , , , , , , , barfs, . IOW, , , - . / - , :)

, do , - - . , - .

Answer 2

!

, VMWare Server, script . , script VM , SSH , , VM, . ( , . , .)

, . ?

. Windows XP, XP SP3 Vista Windows 7.

RedHat Enterprise 5, 5.1, 5.2, 5.3, 5.4 ..

, , OS. Linux , , .

, . , .

Answer 3

, . -, - .

, .

Answer 4

, : "Build with Initial config, Build with update config" . , .