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

ci: run FreeBSD on a VM in github ci, instead of on the Cirrus service #23692

Merged
merged 19 commits into from
Feb 11, 2025

Conversation

spytheman
Copy link
Member

@spytheman spytheman commented Feb 11, 2025

  • ci: add a FreeBSD VM based runner
  • change the name of the new ci
  • port the checks in .cirrus.yml to the new freebsd_ci.yml
  • minor tweaks, pkg install gmake, not make
  • more fixes
  • add sqlite3
  • extract .github/workflows/freebsd_ci.sh, cleanup
  • final cleanup
  • chmod 755 .github/workflows/freebsd_ci.sh
  • check
  • install bash too, use copyback: false
  • minimise the amount of installed packages
  • cleanup
  • restore using make CFLAGS=, to avoid runnign cc -O2, which is too slow on the emulated ARM VM
  • final cleanup, use FreeBSD 14.2 (latest stable as of 2025-02-11; 15 is still a development snapshot)
  • remove .cirrus.yml, since it is not needed anymore
  • migrate freebsd_ci.sh to ci/freebsd_ci.vsh; improve the common ci/ .vsh output
  • cleanup freebsd_ci.yml

Copy link

Connected to Huly®: V_0.6-22112

@spytheman spytheman changed the title run freebsd on github ci ci: run freebsd on github ci, instead of on the Cirrus service Feb 11, 2025
@spytheman spytheman changed the title ci: run freebsd on github ci, instead of on the Cirrus service ci: run FreeBSD on a VM in github ci, instead of on the Cirrus service Feb 11, 2025
@spytheman spytheman merged commit b5d6f40 into vlang:master Feb 11, 2025
45 checks passed
@spytheman spytheman deleted the run_freebsd_on_github_ci branch February 11, 2025 15:35
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.

1 participant