-
Notifications
You must be signed in to change notification settings - Fork 752
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 for FreeBSD #738
Comments
Yes, I think we'd be happy to add freebsd CI to the run. |
Ok, I'll set it up in polling mode. I don't think I need any special access to the mio repository in order to post status reports. Once it's working, I'll ask you to enable commit hooks. |
Do you have an example of how it integrates? It would be nice to ensure that the CI passes for all PRs as well, similar to travis. One option is to have a "fake" travis build that actually delegates to the FreeBSD hardware. |
Here's an example pull request: nix-rust/nix#663 . And if you look at https://github.com/nix-rust/nix/commits/master you can see the status posted for each commit. Nix uses bors, but otherwise it's similar to mio. BuildBot will post its own status notification alongside Travis and Appveyor. |
It uses BuildBot now Issue tokio-rs#738
It uses BuildBot now Issue tokio-rs#738
Would you be interested in running CI tests on FreeBSD? I volunteer to host it. I'm already hosting CI for the nix and mio-aio crates, and it would be no trouble to add this one. If you agree, all that you'll need to do will be to add the GitHub commit hooks.
The text was updated successfully, but these errors were encountered: