Skip to content

[TEST] packaging tests: add windows boxes #27682

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 5 commits into from
Closed

[TEST] packaging tests: add windows boxes #27682

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
cf6f32f
[TEST] packaging tests: add windows boxes
andyb-elastic Dec 5, 2017
8e93e6b
[TEST] Doc comments for vagrant's windows handling
andyb-elastic Dec 8, 2017
e6c646c
Merge branch 'master' into feature/windows-packaging-tests-vagrant
andyb-elastic Dec 8, 2017
d0a58ba
[TEST] Add /tmp install cleanup
andyb-elastic Dec 8, 2017
eca3fee
Merge branch 'master' into feature/windows-packaging-tests-vagrant
andyb-elastic Jan 9, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 10 additions & 2 deletions TESTING.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -363,9 +363,17 @@ quality boxes available in vagrant atlas:

* sles-11

We're missing the following because our tests are very linux/bash centric:
Windows boxes currently supported by the Vagrantfile (but not used in packaging
tests yet) are

* Windows Server 2012
* windows-2012r2 aka Windows Server 2012 R2
* windows-2016 aka Windows Server 2016

Unfortunately licensing issues prevent us from providing Windows boxes for
public use. You can provide your own by setting the environment variables
`VAGRANT_WINDOWS_2012R2_BOX` and/or `VAGRANT_WINDOWS_2016_BOX` with IDs of
images that support remote connections through WinRM and remote Powershell
sessions.

It's important to think of VMs like cattle. If they become lame you just shoot
them and let vagrant reprovision them. Say you've hosed your precise VM:
Expand Down
Loading