Faster CI runners
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.4k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
Previously Embark used paid runners to get faster builds. As part of the transition we went to the slower Github action runners. We should look into getting credits and/or sponsors for faster CI if it is a problem.
This is what they used to have:
- os: ubuntu-20.04-16core
target: x86_64-unknown-linux-gnu
- os: windows-2022-16core
target: x86_64-pc-windows-msvc
- os: macOS-latest-xl
target: x86_64-apple-darwin
- os: ubuntu-20.04-16core
target: aarch64-linux-android
host: x86_64-unknown-linux-gnu
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
No specific workflow file or test is named. Start by reviewing the repository's GitHub Actions runner configuration and compare it with the listed 16-core runners; done means determining whether slower builds are a problem and identifying viable credits or sponsors for faster CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100