Windows Server 2016 testing environment #23
Conversation
WIP chocolatey-test-environment/issues/20 Upgrade Git WIP chocolatey-test-environment/issues/21 Upgrade 7-Zip See https://groups.google.com/d/msg/chocolatey/rNITSnb9P9k/IhC9oMr7BQAJ
Closes chocolatey-community#19 Closes chocolatey-community#20 Closes chocolatey-community#21 Closes chocolatey-community#22 See hashicorp/vagrant#9138 for an issues regarding Windows Server 2016 and powershell provisioners. See https://github.com/StefanScherer/packer-windows for packer templates
| if (Get-Command "choco.exe" -ErrorAction SilentlyContinue) | ||
| { | ||
| "7zip", "bitvise-ssh-server", "git", "notepadplusplus" | ForEach-Object -Process {choco install $_} | ||
| } |
There was a problem hiding this comment.
No need for these to be here. They were pre-installed on the older system
There was a problem hiding this comment.
See https://github.com/chocolatey/chocolatey-test-environment/issues the tool chain is very old and I'd like to have the tools upgraded.
We can fork the packer project and add the tools in packer but this keeps the design clean and installs current tools in this project.
See my comments about using chocolatey to install the tools because I view the test environment as testing chocolatey packages and not chocolatey itself it's ok(?) to use chocolate to install the latest version of tools?
There was a problem hiding this comment.
See my comments about using chocolatey to install the tools because I view the test environment as testing chocolatey packages and not chocolatey itself it's ok(?) to use chocolate to install the latest version of tools?
That's likely fine.
| @@ -14,7 +14,7 @@ end | |||
| Vagrant.configure("2") do |config| | |||
| # This setting will download the atlas box at | |||
| # https://atlas.hashicorp.com/ferventcoder/boxes/win2012r2-x64-nocm | |||
| config.vm.box = "ferventcoder/win2012r2-x64-nocm" | |||
| config.vm.box = "BasicTheProgram/windows_2016" | |||
There was a problem hiding this comment.
I am not sure we'd convert to another box, apologies. We would need to really review it for safety and security, as this test environment is used in many environments.
And do you have vmware_fusion, hyper-v, and virtualbox versions?
There was a problem hiding this comment.
I do not have fusion, or hyper-v versions, but packer has the ability to build all of the above with a pretty simple command line evocation.
See my comments in the google group about having git branches for each version of windows or having multiple versions of Windows supported in the VagrantFile.
I have the need for a Windows 2016 testing environment, thus these changes. I don't want to deprecated or diminish the Server 2012 R2 stuff, ideally supporting multiple test environments is the goal. Just need guidance from you on how to do that.
And, ideally, you'd take over the official config.vm.box stuff. Probably build via packer to make it easier for people to contribute to the test environment?
| config.vm.provision :shell, :path => "shell/InstallNet4.ps1", privileged: false | ||
| config.vm.provision :shell, :path => "shell/InstallChocolatey.ps1", privileged: false | ||
| config.vm.provision :shell, :path => "shell/NotifyGuiAppsOfEnvironmentChanges.ps1",privileged: false | ||
| config.vm.provision :shell, :path => "shell/InstallToolchain.ps1", privileged: false |
There was a problem hiding this comment.
Why non-privileged? It needs to succeed, which is highly likely to need to run with admin on the VM. Not sure I understand this change
There was a problem hiding this comment.
See hashicorp/vagrant#9138 for the ugly details. Looks like a change in Windows Server 2016 Build 14393.rs1_release.170917-1700.
Happy to change it if you know another work-around for Windows Server 2016. If you read the ticket the upstream maintainer of the packer scripts reports that this specific build of Windows Server 2016 has the problem.
So can work around it or wait(?) for Microsoft to change thing back?
…latey-test-environment into win2012r2-x64-nocm
…t-environment into my_win2012r2-x64-nocm
Windows Server 2016 WIP chocolatey-community#31 but for Windows Server 2016
Get the Windows Server 2016 from Vagrant Cloud
…nvironment into windows_2016
Windows Server 2016 testing environment with updated tool chain.