-
Notifications
You must be signed in to change notification settings - Fork 82
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
Add basic FreeBSD CI using Cirrus CI #923
Conversation
This will need Cirrus CI to be installed on this repo. |
950ec6f
to
a1ccddf
Compare
Let's discuss this a bit further with @rnijveld before merging. Maybe we should switch to a system where a "lighter" CI runs on |
a1ccddf
to
e1abd2f
Compare
e1abd2f
to
b7dd9e1
Compare
b7dd9e1
to
37fa28b
Compare
Closed in favor of #937 |
You closed the wrong one :-) |
Oops |
3b06b9c
to
b1e4edb
Compare
I'm testing this on my personal repo for a while to see how it behaves. At ntpd-rs, they test on FreeBSD using a vm which sounds like it's more of a hassle than this. |
b1e4edb
to
bc79538
Compare
https://github.com/squell/sudo-rs/runs/37021119441 Looks like it's not guaranteed that FreeBSD image stay around for a reasonably long time. At the same time it was easy to fix (apparently these are linked to the "official FreeBSD VMs on Google Cloud Platform are supported.") |
This currently only runs unit tests and not the compliance tests.
a95ef37
to
390462a
Compare
This currently only runs unit tests and not the compliance tests.
Cirrus CI is the only CI provider I'm aware of which supports FreeBSD out of the box. It does have the disadvantage though that on the free tier it can take several minutes before a CI job actually starts.