Travis build stages #56
Conversation
laughedelic
force-pushed
the
travis-build-stages
branch
from
5e33603
to
6dcabdd
Compare
laughedelic
force-pushed
the
travis-build-stages
branch
from
6dcabdd
to
e550cb9
Compare
.travis.yml
Outdated
| script: ./bin/scalafmt --test | ||
| - env: TEST="languageserver/test" | ||
| script: sbt $TEST | ||
| - env: TEST="tests.ctags" |
There was a problem hiding this comment.
I don't think we need to split the tests into different matrices yet. In #51 I added tests tests.compiler, which would not be caught by this. Full test suite still runs in <2-3 minutes.
There was a problem hiding this comment.
I suspect we'll want this later down the road however once we get heavier integration tests 👍
There was a problem hiding this comment.
OK. Addressed in cb64f24
And I just checked that it doesn't release on normal push to master: https://travis-ci.org/scalameta/language-server/builds/306921020 🎉 Finally it works! |
|
Sweet! Build stages looks very promising, we have had a lot of problems with this in the scalameta build where we publish over 70 artifacts! |
Here I replace CI script and
deployblock with Build Stages (a beta feature of Travis). It allows you to run release stage only if all jobs from the test stage have passed (without stagesdeployblock is executed in every job, so you need to workaround it with complicated conditions).I also show here how different test-suites can be run in parallel. It's probably not that useful now, so I can remove it, but it could be useful when we have more time-consuming tests.
Also note that
TESTenv var is used just to distinguish jobs:I hope this also fixes the problem with releasing on merge (and not on normal push). We'll see when we merge this PR 🤞