Remove old CI config (#5572)

* Remove old CI config

Signed-off-by: Yuki Okushi <jtitor@2k36.org>

* Replace outdated badges

Signed-off-by: Yuki Okushi <jtitor@2k36.org>

---------

Signed-off-by: Yuki Okushi <jtitor@2k36.org>
This commit is contained in:
Yuki Okushi 2023-01-30 07:44:58 +09:00 committed by GitHub
parent 61d82acf53
commit 9cc0af5407
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 2 additions and 84 deletions

View File

@ -21,6 +21,3 @@ indent_size = unset
indent_style = unset
trim_trailing_whitespace = unset
insert_final_newline = unset
[appveyor.yml]
end_of_line = unset

View File

@ -1,77 +0,0 @@
sudo: false
language: rust
rust: nightly
os: linux
cache:
directories:
- $HOME/.cargo
addons:
apt:
packages:
- libcurl4-openssl-dev
- libelf-dev
- libdw-dev
matrix:
include:
- env: DEPLOY=LINUX
- env: CFG_RELEASE_CHANNEL=beta
- os: osx
- env: INTEGRATION=bitflags
- env: INTEGRATION=chalk
- env: INTEGRATION=crater
- env: INTEGRATION=error-chain
- env: INTEGRATION=glob
- env: INTEGRATION=log
- env: INTEGRATION=mdbook
- env: INTEGRATION=packed_simd
- env: INTEGRATION=rust-semverver
- env: INTEGRATION=stdsimd TARGET=x86_64-unknown-linux-gnu
- env: INTEGRATION=tempdir
- env: INTEGRATION=futures-rs
allow_failures:
# Using old configuration option
- env: INTEGRATION=rand
# Doesn't build - keep this in allow_failures as it's fragile to breaking changes of rustc.
- env: INTEGRATION=rust-clippy
# Doesn't build - seems to be because of an option
- env: INTEGRATION=packed_simd
# Doesn't build - a temporal build failure due to breaking changes in the nightly compilre
- env: INTEGRATION=rust-semverver
# can be moved back to include section after https://github.com/rust-lang-nursery/failure/pull/298 is merged
- env: INTEGRATION=failure
# `cargo test` doesn't finish - disabling for now.
# - env: INTEGRATION=cargo
script:
- |
if [ -z ${INTEGRATION} ]; then
export CFG_RELEASE_CHANNEL=nightly
export CFG_RELEASE=nightly
cargo build
cargo test
cargo test -- --ignored
else
./ci/integration.sh
fi
after_success:
- if [ -z ${INTEGRATION} ]; then travis-cargo coveralls --no-sudo; fi
before_deploy:
# TODO: cross build
- cargo build --release --target=x86_64-unknown-linux-gnu
- tar czf rustfmt-x86_64-unknown-linux-gnu.tar.gz Contributing.md Design.md README.md -C target/x86_64-unknown-linux-gnu/release/rustfmt rustfmt
deploy:
provider: releases
api_key:
secure: "your own encrypted key"
file:
- rustfmt-x86_64-unknown-linux-gnu.tar.gz
on:
repo: nrc/rustfmt
tags: true
condition: "$DEPLOY = LINUX"
skip_cleanup: true

View File

@ -1,4 +1,4 @@
# rustfmt [![Build Status](https://travis-ci.com/rust-lang/rustfmt.svg?branch=master)](https://travis-ci.com/rust-lang/rustfmt) [![Build Status](https://ci.appveyor.com/api/projects/status/github/rust-lang/rustfmt?svg=true)](https://ci.appveyor.com/project/rust-lang-libs/rustfmt) [![crates.io](https://img.shields.io/crates/v/rustfmt-nightly.svg)](https://crates.io/crates/rustfmt-nightly) [![Travis Configuration Status](https://img.shields.io/travis/davidalber/rustfmt-travis.svg?label=travis%20example)](https://travis-ci.org/davidalber/rustfmt-travis)
# rustfmt [![linux](https://github.com/rust-lang/rustfmt/actions/workflows/linux.yml/badge.svg?event=push)](https://github.com/rust-lang/rustfmt/actions/workflows/linux.yml) [![mac](https://github.com/rust-lang/rustfmt/actions/workflows/mac.yml/badge.svg?event=push)](https://github.com/rust-lang/rustfmt/actions/workflows/mac.yml) [![windows](https://github.com/rust-lang/rustfmt/actions/workflows/windows.yml/badge.svg?event=push)](https://github.com/rust-lang/rustfmt/actions/workflows/windows.yml) [![crates.io](https://img.shields.io/crates/v/rustfmt-nightly.svg)](https://crates.io/crates/rustfmt-nightly)
A tool for formatting Rust code according to style guidelines.
@ -7,9 +7,7 @@ If you'd like to help out (and you should, it's a fun project!), see
Conduct](CODE_OF_CONDUCT.md).
You can use rustfmt in Travis CI builds. We provide a minimal Travis CI
configuration (see [here](#checking-style-on-a-ci-server)) and verify its status
using another repository. The status of that repository's build is reported by
the "travis example" badge above.
configuration (see [here](#checking-style-on-a-ci-server)).
## Quick start