This patch modifies the Travis build pipeline to include multiple
[build stages](https://docs.travis-ci.com/user/build-stages/). CI now
progresses in the following steps:
- First, `cargo check` is run on `stable` only.
If it fails, the build is considered failed.
This is so that we can fail fast for obviously botched commits.
- Then, unit and doc tests are run for all targets.
If any non-nightly tests fail, the build fails.
- Then, integration tests with
[GreenMail](http://www.icegreen.com/greenmail/) are run on Linux for
all Rust targets. We can't run them on macOS because it doesn't
support the Docker service.
If any non-nightly tests fail, the build fails.
- Then, `rustfmt` and `clippy` are both run on *beta* and on nightly.
We use beta instead of stable to try to give ourselves some headroom
for changes coming down the pike. The lints are only run on Linux,
because the platform shouldn't matter.
If any beta lints fail, the build fails.
- And finally, we generate a coverage report on nightly on Linux.
This can only run on nightly because tarpaulin requires nightly.
It's only run on Linux, because we want to include integration tests.
Note that the coverage stage has its own cache
(`CACHE_NAME=coverage`) because the only thing it caches is cargo
tarpaulin (the rust/cargo cache is cleaned before exit).
Fixes#48.
Specifically, if a test doesn't clean up nicely after itself, running it
a second time for checking coverage might make it fail! We restart the
docker server so that all the server state is erased, which should
mitigate that.
travis-cargo no longer works with coveralls, and appears
to be unmaintained. This change use regular cargo to
build and test. It now uses cargo-travis to push test
results to coveralls. This will also build nightly, and
only push test results on the stable build.
* Use docs.rs for documentation
This would also allow deleting the `gh-pages` branch (which is pretty large).
I'd also recommend adding `badges` and `categories` to make the crates.io page more useful (see [this](http://www.integer32.com/2017/01/20/categories-and-ci-badges.html)), but I'll leave that up to you.
* Remove more references to old docs
