3 ms·
>So the most effective thing to do to take Rust FreeBSD support to the next level is to figure out a way to get the CI to run tests. If I were to set up my own
by eriknstr 10y ago
>So the most effective thing to do to take Rust FreeBSD support to the next level is to figure out a way to get the CI to run tests.
If I were to set up my own FreeBSD buildbot for commits to the Rust repos, would result reports from my buildbot be welcome? Would automatic reports be useful to you, or should I manually inspect failures and write up a bug report / pull request with fixes for issues that arise? If automatic, how could I best integrate reports of failure with your development process for Rust?
>There may be opportunities in the future for paid Rust platform support, where if a motivated party donates the right amount of money, we'll make it happen. I think that will have to happen to get some of the remaining platforms up to production quality.
I like this idea though I don't have a lot of money to spend myself currently.
- brson 10y agoWe no longer use buildbot for our CI. We have a "meta CI" system called bors/homu that integrates with other CI, currently Travis and AppVeyor. bors works with any service that can post a result to a GitHub PR. So the plan for supporting further architectures is to create a small custom runner that builds, tests and posts to the PR. That code does not exist yet, but if it appeared there are likely several upcoming architectures that could make use of it. With that tool, we could allow contributors to set up their own integration bots and hook into our CI.