Illumos CI
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
As came up in https://github.com/uutils/coreutils/pull/5489, we'd love to have CI for Illumos!
Based on the advice from @Toasterson (https://github.com/uutils/coreutils/pull/5489#issuecomment-1793402756), that should probably be done using a Vagrant box:
https://github.com/twpayne/chezmoi/blob/v2.9.3/.github/workflows/main.yml#L173-L191
Running the CI like that probably will uncover some issues, which means that we'll have to disable some utils and tests (temporarily) or fix the issues.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the advice in pull request 5489 and the referenced chezmoi .github/workflows/main.yml Vagrant workflow. Set up Illumos CI using a Vagrant box, then run the workflow to identify affected utilities and tests; done means the CI job runs successfully with temporary exclusions or fixes documented by the resulting failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100