on master help sign in
Do not use global ‘env’ in the travis script

Changing the ‘env’ value discards the caches, which is unacceptable.

commit9257f5f417ae5784557cbeed7ed9ca273aaf22c7 authorMark Karpov <markkarpov92@gmail.com> dateThu 23 Apr 2020, 22:53 (6 years ago) parentc2c2ba3
1 file changed+6−9
.travis.yml+6−9
.travis.yml+6−9
@@ -7,12 +7,6 @@ cache:
77 - ~/.cabal/packages
88 - ~/.cabal/store
99
10−env:
11− global:
12− # To avoid re-compilation it is important to use exactly the same
13− # configuration for all steps.
14− - CABAL_CONFIG="--enable-tests --enable-benchmarks --flags=dev"
15−
1610matrix:
1711 include:
1812 - env: CABALVER=3.0 GHCVER=8.6.5
@@ -31,11 +25,14 @@ install:
3125 - travis_retry cabal new-update
3226
3327script:
28+ # To avoid re-compilation it is important to use exactly the same
29+ # configuration for all steps.
30+ - export CONFIG="--enable-tests --enable-benchmarks --flags=dev"
3431 - cabal format
3532 - git diff --exit-code --color=always
36− - cabal new-build $CABAL_CONFIG
37− - cabal new-test $CABAL_CONFIG
38− - cabal new-haddock $CABAL_CONFIG
33+ - cabal new-build $CONFIG
34+ - cabal new-test $CONFIG
35+ - cabal new-haddock $CONFIG
3936 - cabal new-sdist
4037
4138notifications: