PolytreeDE/alacritty
1
0
Fork 0
mirror of https://github.com/alacritty/alacritty.git synced 2024-11-11 13:51:01 -05:00
Code Releases Activity
alacritty/.travis.yml

62 lines
1.6 KiB
YAML
Raw Normal View History

Add function for listing font names on linux This function isn't exactly useful, but it's working ffi with the fontconfig library. Woo! Next step will be returning some objects with more information (like font path so we can start rendering glyphs!).
2016-02-21 18:20:03 -05:00
language: rust
Publish Github releases from Travis This release introduces some config to automatically build deploy a binaries on the github release page using travis. The build only happens when a commit is tagged and it uses the stable version of rust. The main travis sections (install/script/before_deploy) have been moved out of the .travis.yml to make it easier to read, maintain and extend the different steps of the CI process. Since checking for the Rust version in CI is enough to know if clippy should be used or not, the environment variable `CLIPPY` has also been removed, which further allowed simplifying the CI process. Besides the executables, some auxillary files are now also published as part of a release when they have changed since the last tagged Alacritty release. This should make it clear for returning users when a new version of a specific auxillary file is required. Instead of using the 14.04 image which travis provides by default, an 18.04 docker image is used to build the output binaries for Linux. This affects both the .deb and the .tar.gz binary. The advantage of this is that while binaries compiled on 14.04, do not work on 18.04, it does work the other way around. The generated .tar.gz binary has been tested on 18.04, Debian, Fedora and Archlinux and all systems were able to run it without any warnings or errors.
2018-11-03 11:08:30 -04:00
services:
- docker
Add function for listing font names on linux This function isn't exactly useful, but it's working ffi with the fontconfig library. Woo! Next step will be returning some objects with more information (like font path so we can start rendering glyphs!).
2016-02-21 18:20:03 -05:00
Add support for Windows (#1374) Initial support for Windows is implemented using the winpty translation layer. Clipboard support for Windows is provided through the `clipboard` crate, and font rasterization is provided by RustType. The tty.rs file has been split into OS-specific files to separate standard pty handling from the winpty implementation. Several binary components are fetched via build script on windows including libclang and winpty. These could be integrated more directly in the future either by building those dependencies as part of the Alacritty build process or by leveraging git lfs to store the artifacts. Fixes #28.
2018-10-16 13:02:52 -04:00
git:
depth: 1
Add macOS to CI matrix
2016-06-14 10:53:45 -04:00
os:
- linux
- osx
Add support for Windows (#1374) Initial support for Windows is implemented using the winpty translation layer. Clipboard support for Windows is provided through the `clipboard` crate, and font rasterization is provided by RustType. The tty.rs file has been split into OS-specific files to separate standard pty handling from the winpty implementation. Several binary components are fetched via build script on windows including libclang and winpty. These could be integrated more directly in the future either by building those dependencies as part of the Alacritty build process or by leveraging git lfs to store the artifacts. Fixes #28.
2018-10-16 13:02:52 -04:00
- windows
Add macOS to CI matrix
2016-06-14 10:53:45 -04:00
Add function for listing font names on linux This function isn't exactly useful, but it's working ffi with the fontconfig library. Woo! Next step will be returning some objects with more information (like font path so we can start rendering glyphs!).
2016-02-21 18:20:03 -05:00
rust:
Bump minimum supported Rust version to 1.34.0
2019-07-30 18:13:51 -04:00
- 1.34.0
Alacritty now compiles on stable Rust :tada:
2017-02-02 23:50:48 -05:00
- stable
Make Travis test alacritty on nightly Rust, but allow failures This allows us to notice and report any regressions that have occured on nightly, without requiring tests to pass on nightly for the entire build to succeed. The `fast_finish` flag will cause Travis to mark the build as successful if the only builds still running are allowed to fail (e.g. `nightly`). This allows us to manually inspect builds (or implement some form of notifications) to see if any nightly regressions have occured, without slowing down the overall build time.
2017-06-14 12:56:45 -04:00
- nightly
matrix:
fast_finish: true
Fix i386 CI releases The i386 CI releases were still using x86_64 platforms for building the output binaries, as a result the produced binaries did not work properly on i386 systems. The maximum time of 50 minutes was exceeded when Alacritty tries to build for all Linux platforms, this was because it was effectively compiling Alacritty from scratch four times. By making use of the previous build artifacts, it's possible to cut this down to two compiles using the `--no-build` option of `cargo-deb`.
2018-11-14 18:47:13 -05:00
include:
- if: tag IS present
os: linux
rust: stable
env: ARCH=i386
Move clippy tests to stable The clippy tests had to be run on nightly previously since it wasn't available with the stable compiler yet, however this had the potential to fail a lot since not all nightly builds offer clippy. Since clippy is now available for stable rust, moving clippy to a stable build should make sure that the failure rate of the CI job is cut down to a minimum. This fixes https://github.com/jwilm/alacritty/issues/2007.
2019-01-23 17:04:45 -05:00
- name: "Clippy Linux"
os: linux
env: CLIPPY=true
rust: stable
- name: "Clippy OSX"
os: osx
env: CLIPPY=true
rust: stable
- name: "Clippy Windows"
os: windows
env: CLIPPY=true
rust: stable
Add rustfmt style guide
2019-03-30 12:48:36 -04:00
- name: "Rustfmt"
os: linux
env: RUSTFMT=true
rust: nightly
Make Travis test alacritty on nightly Rust, but allow failures This allows us to notice and report any regressions that have occured on nightly, without requiring tests to pass on nightly for the entire build to succeed. The `fast_finish` flag will cause Travis to mark the build as successful if the only builds still running are allowed to fail (e.g. `nightly`). This allows us to manually inspect builds (or implement some form of notifications) to see if any nightly regressions have occured, without slowing down the overall build time.
2017-06-14 12:56:45 -04:00
allow_failures:
- rust: nightly
Add function for listing font names on linux This function isn't exactly useful, but it's working ffi with the fontconfig library. Woo! Next step will be returning some objects with more information (like font path so we can start rendering glyphs!).
2016-02-21 18:20:03 -05:00
Publish Github releases from Travis This release introduces some config to automatically build deploy a binaries on the github release page using travis. The build only happens when a commit is tagged and it uses the stable version of rust. The main travis sections (install/script/before_deploy) have been moved out of the .travis.yml to make it easier to read, maintain and extend the different steps of the CI process. Since checking for the Rust version in CI is enough to know if clippy should be used or not, the environment variable `CLIPPY` has also been removed, which further allowed simplifying the CI process. Besides the executables, some auxillary files are now also published as part of a release when they have changed since the last tagged Alacritty release. This should make it clear for returning users when a new version of a specific auxillary file is required. Instead of using the 14.04 image which travis provides by default, an 18.04 docker image is used to build the output binaries for Linux. This affects both the .deb and the .tar.gz binary. The advantage of this is that while binaries compiled on 14.04, do not work on 18.04, it does work the other way around. The generated .tar.gz binary has been tested on 18.04, Debian, Fedora and Archlinux and all systems were able to run it without any warnings or errors.
2018-11-03 11:08:30 -04:00
install: ci/install.sh
script: ci/script.sh
before_deploy: ci/before_deploy.sh
deploy:
provider: releases
api_key:
secure: G6JZgC5qKZyxEmuu2eMscDO45iOhBjiCSKuO8gxywqm+4DbMZm7y2OSbQCEmnIFqEgi+DLkrH/A7e8LDngQj3lBvRnWkIcszG5ubDm8jsqckXXxjI0cy5q8jJ7s5zZXH2IdXifY59KN9V4iHPwCJlyEE7Aj9JrJLFaVhvaowlSYib9DuDibDX/2u8qZ+gP2D/TntiBlFi8SgiDPd7GrZWmNsxJR9edyYbKx9izROp+4q7KAa0Xqak/Zvg72JZnARiKPmBxESEoYYXFcRgRZD9VvjmQ/il6WcHlGSqqn1TRBtIVl8L/1I5/xBJ6KMegP9Jlh7ybm1JPfX108V5d9a9CyqvRYHrhbkHkf5oktizsgw2WyANwiBhEngliMFuUyT0826BEPtkA4TiD7lQXyvO749INdJsqUlMLLuQNpU9/7ShBcRapbGp6AjWH8yxV9ciNMpNexAaxkupYc2NaU6EAC/C34HAtTdfN+gyvrtnF1ISrPmmGj8YQRiBUsa4TxghsNPbPHWAgMfR5lFp3dONz0oIydhW/AFgpn+7BVvoIW2z8hXiRttseZHv6akeSjFC5vYObR3UdL/NiuvCjZRiYryL0Be/rI83ug8xELVFBBcv4PxcHEsXWT7EMd3QTiPoCwNKoSoBLk8hPFPAGRXULiSDFENKoJAc4A7zJyMiYY=
skip_cleanup: true
file_glob: true
file: "./target/deploy/*"
on:
tags: true
rust: stable
Remove deployment script from clippy builds
2019-02-10 18:15:00 -05:00
condition: $CLIPPY != true
Publish Github releases from Travis This release introduces some config to automatically build deploy a binaries on the github release page using travis. The build only happens when a commit is tagged and it uses the stable version of rust. The main travis sections (install/script/before_deploy) have been moved out of the .travis.yml to make it easier to read, maintain and extend the different steps of the CI process. Since checking for the Rust version in CI is enough to know if clippy should be used or not, the environment variable `CLIPPY` has also been removed, which further allowed simplifying the CI process. Besides the executables, some auxillary files are now also published as part of a release when they have changed since the last tagged Alacritty release. This should make it clear for returning users when a new version of a specific auxillary file is required. Instead of using the 14.04 image which travis provides by default, an 18.04 docker image is used to build the output binaries for Linux. This affects both the .deb and the .tar.gz binary. The advantage of this is that while binaries compiled on 14.04, do not work on 18.04, it does work the other way around. The generated .tar.gz binary has been tested on 18.04, Debian, Fedora and Archlinux and all systems were able to run it without any warnings or errors.
2018-11-03 11:08:30 -04:00
repo: jwilm/alacritty
branch: master
Copy permalink