use travis for mima and whitesource, remain no jenkins for tests (in parallel) (#24968)

* travis config from akka-http

* amend CONTRIBUTING to explain our tests

* amend wording in CONTRIBUTING

* new whitesource key

* remove instead of comment deployment things

* Update CONTRIBUTING.md

* exclude new module in 2.5 from appearing in 2.4 previous mima artifacts

* fix mima on 2.12
This commit is contained in:
Konrad `ktoso` Malawski 2018-04-24 22:58:54 +09:00 committed by GitHub
parent 80eff85527
commit 0f676cb6f1
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
6 changed files with 56 additions and 6 deletions

View file

@ -386,13 +386,16 @@ tested it becomes an officially supported Akka feature.
## Continuous integration
Each project should be configured to use a continuous integration (CI) tool (i.e. a build server à la Jenkins).
Akka currently uses a combination of Jenkins and Travis for Continuous Integration:
* Jenkins [runs the tests for each PR](https://jenkins.akka.io:8498/job/pr-validator-per-commit-jenkins/)
* Jenkins [runs a nightly test suite](https://jenkins.akka.io:8498/view/Nightly%20Jobs/job/akka-nightly/)
* Travis [checks dependency licenses for all PR's](https://travis-ci.org/akka/akka)
The [Jenkins server farm](https://jenkins.akka.io/), sometimes referred to as "the Lausanne cluster", is sponsored by Lightbend.
Lightbend is sponsoring a [Jenkins server farm](https://jenkins.akka.io/), sometimes referred to as "the Lausanne cluster".
The cluster is made out of real bare-metal boxes, and maintained by the Akka team (and other very helpful people at Lightbend).
In addition to PR validation the cluster is also used for nightly and performance test runs.
## Related links
* [Akka Contributor License Agreement](http://www.lightbend.com/contribute/cla)