PolytreeDE/alacritty
1
0
Fork 0
mirror of https://github.com/alacritty/alacritty.git synced 2024-11-25 14:05:41 -05:00
Code Releases Activity
alacritty/.github/workflows/ci.yml

28 lines
480 B
YAML
Raw Normal View History

Migrate from Travis CI to GitHub Actions This removes all CI builds from travis-ci, due to their recent changes in policy and harsh limitations on builds. With build times over 2 hours, it was a significant hindrance to development. Instead of Travis CI, the CI is now split on Sourcehut and GitHub. Since Sourcehut only supports Linux/BSD, all builds on those operating systems are executed there. The GitHub Actions CI is used to build for Windows/macOS, which are not available on Sourcehut. Since asset deployment for releases requires builds on all platforms, this is also done on GitHub actions. Though the new `upload_asset.sh` script makes sure that migration in the future is fairly simple and we do not tie ourselves to the overly complicated GitHub Actions ecosystem.
2020-11-06 18:52:56 -05:00
name: CI
on: [push, pull_request]
env:
CARGO_TERM_COLOR: always
jobs:
build:
strategy:
matrix:
os: [windows-latest, macos-latest]
runs-on: ${{ matrix.os }}
steps:
- uses: actions/checkout@v2
Reduce number of GitHub Actions CI builds By reducing the number of CI jobs for GitHub actions, it should be possible to get a faster overview over the status of all CI jobs. While this does increase the total build time of GitHub Actions by reducing parallelization, it should still finish within the SourceHut CI times.
2020-11-17 08:21:51 -05:00
- name: Stable
Migrate from Travis CI to GitHub Actions This removes all CI builds from travis-ci, due to their recent changes in policy and harsh limitations on builds. With build times over 2 hours, it was a significant hindrance to development. Instead of Travis CI, the CI is now split on Sourcehut and GitHub. Since Sourcehut only supports Linux/BSD, all builds on those operating systems are executed there. The GitHub Actions CI is used to build for Windows/macOS, which are not available on Sourcehut. Since asset deployment for releases requires builds on all platforms, this is also done on GitHub actions. Though the new `upload_asset.sh` script makes sure that migration in the future is fairly simple and we do not tie ourselves to the overly complicated GitHub Actions ecosystem.
2020-11-06 18:52:56 -05:00
run: cargo test
Run clippy on MSRV Since not all suggested clippy lints by stable clippy are supported on the MSRV of Alacritty, this commit moves the clippy checks to the MSRV. Unfortunately this will mean that our lints might be significantly behind, however it ensures our CI never blocks any code that should be valid. Developers themselves of course can still run the latest clippy to follow the up to date recommendations.
2021-02-27 10:06:22 -05:00
- name: Oldstable
run: |
Update dependencies
2021-07-13 22:18:40 -04:00
rustup default 1.46.0
Run clippy on MSRV Since not all suggested clippy lints by stable clippy are supported on the MSRV of Alacritty, this commit moves the clippy checks to the MSRV. Unfortunately this will mean that our lints might be significantly behind, however it ensures our CI never blocks any code that should be valid. Developers themselves of course can still run the latest clippy to follow the up to date recommendations.
2021-02-27 10:06:22 -05:00
cargo test
Reduce number of GitHub Actions CI builds By reducing the number of CI jobs for GitHub actions, it should be possible to get a faster overview over the status of all CI jobs. While this does increase the total build time of GitHub Actions by reducing parallelization, it should still finish within the SourceHut CI times.
2020-11-17 08:21:51 -05:00
- name: Clippy
run: |
rustup component add clippy
cargo clippy --all-targets
Copy permalink