Adjust Vagrantfiles for automated build #27081
Draft
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.
Make some changes to our portability testing
Vagrantfile
s to be more amenable to automated testing via a Jenkins job.Changes:
freebsd/
boxes tobento/
boxes, for a few reasons:freebsd/
boxes for several recent FreeBSD releases -- we already used bento for one.bento
boxes are built with a more recent VirtualBox and appear to come withsudo
, fixing some issues I encountered trying to use thefreebsd
boxes on a test system.http[s]_proxy
env vars into the VM permanently, so they function on systems behind a proxy.To be merged alongside a CI change adding such a Jenkins job.
Resolves https://github.com/Cray/chapel-private/issues/2000.
[reviewer info placeholder]
Testing: