cothority

cothority copied to clipboard

The test for Travis to go over the cothority-repo is taking anywhere from 30' to 1h, depending on the load of Travis.

Some ideas to speed it up:

1. reduce the number of tests + easy to do - test-coverage decreases
2. replace travis with circleCI and run it on an EPFL machine with more oomph + keep all tests - need to rewrite the .travis.yml - need to setup circleCI
3. replace travis with Jenkins, as Jenkins is already setup - https://resources.github.com/whitepapers/practical-guide-to-CI-with-Jenkins-and-GitHub/ + keep all tests - rewrite .travis.yml
4. rewrite tests to be faster and more unit-test based + keep travis - lots of work
5. retry for/rewrite tests to be parallel; currently goveralls does each dir individually, and sequentially in each + harder, better, faster, stronger - might be a lot of work

Low-hanging fruits

A. Only test go 1.12 (but keep builds for go 1.11 and go 1.12)

hi also recommend to look at drone CI, as it's easy to setup + you may cache builds on some external storage for faster execution

We are removing Travis testing for Go 1.12, but we should make sure that Jenkins still runs it.

With travis each job in a stage is run in parallel, so we don't gain much by removing go 1.12.x

@nkcr travis only runs a limited number of jobs in parallel, to avoid overloading of the machines. There are two ways to get around this:

• pay more money to get more parallel builds
• install your own CI infrastructure, e.g. in Kubernetes, then you pay as you go...