Added support for multiple OSes for vagrant #4947
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
27 tasks
teddytpc1
approved these changes
Feb 9, 2024
fcaffieri
approved these changes
Feb 9, 2024
teddytpc1
approved these changes
Feb 14, 2024
teddytpc1
deleted the
enhancement/4862-dtt1-iteration-3-allocation-module-improve-sizes-and-os-for-vagrant-provider
branch
Closed
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Close #4862
Updated the vagrantboxes for Vagrant deployment:
Ubuntu 16.04 amd64: #4862 (comment)
Ubuntu 18.04 amd64: #4862 (comment)
Ubuntu 20.04 amd64: #4862 (comment)
Ubuntu 22.04 #4862 (comment)
Debian 9 #4862 (comment)
Debian 10 amd64: #4862 (comment)
Debian 11 amd64: #4862 (comment)
Debian 12 amd64: #4862 (comment)
Oracle Linux 7 amd64: #4862 (comment)
Oracle Linux 8 amd64: #4862 (comment)
Oracle Linux 9 amd64: #4862 (comment)
openSUSE 15 amd64: #4862 (comment)
openSUSE Tumbleweed amd64: #4862 (comment)
Centos 7 amd64: #4862 (comment)
Centos 8 amd64: #4862 (comment)
Centos 9 amd64: #4862 (comment)
Red Hat 7 amd64: #4862 (comment)
Red Hat 8 amd64: #4862 (comment)
Red Hat 9 amd64: #4862 (comment)
Amazon Linux 2 amd64: #4862 (comment)
Fedora 28 #4862 (comment)
Fedora 29 #4862 (comment)
Fedora 31 #4862 (comment)
Fedora 32 #4862 (comment)
Fedora 37 amd64: #4862 (comment)
Fedora 38 amd64: #4862 (comment)
Rocky Linux 8 amd64: #4862 (comment)
Rocky Linux 9 amd64: #4862 (comment)
Windows desktop 10: #4862 (comment)
Windows desktop 11: #4862 (comment)
Windows server 2012: #4862 (comment)
Windows server 2012 R2: #4862 (comment)
Windows server 2016: #4862 (comment)
Windows server 2019: #4862 (comment)
Windows server 2022: #4862 (comment)
In the tests I encountered a problem in the length of characters that the VM name required in VirtualBox, for this reason I had to modify the code so that the instance id is set as the VM name