Skip to content
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.

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

Adjust Vagrantfiles for automated build #27081

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

arifthpe
Copy link
Contributor

@arifthpe arifthpe commented Apr 9, 2025

Make some changes to our portability testing Vagrantfiles to be more amenable to automated testing via a Jenkins job.

Changes:

  • Switched from official freebsd/ boxes to bento/ boxes, for a few reasons:
    • There are no freebsd/ boxes for several recent FreeBSD releases -- we already used bento for one.
    • Consistency with the above.
    • The bento boxes are built with a more recent VirtualBox and appear to come with sudo, fixing some issues I encountered trying to use the freebsd boxes on a test system.
  • Added a provisioning step which runs a script to propagate http[s]_proxy env vars into the VM permanently, so they function on systems behind a proxy.
  • Also updated to testing only the currently supported FreeBSD releases while here.

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:

  • manual run of my test version of job

@arifthpe arifthpe force-pushed the vagrant-automation branch from 98936e7 to a869bb7 Compare April 10, 2025 15:32
@arifthpe arifthpe force-pushed the vagrant-automation branch from a869bb7 to 978950c Compare April 10, 2025 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants