summaryrefslogtreecommitdiff
path: root/.travis.yml
diff options
context:
space:
mode:
authorEvgeny Vereshchagin <evvers@ya.ru>2019-06-14 20:42:19 +0200
committerEvgeny Vereshchagin <evvers@ya.ru>2019-06-14 20:42:19 +0200
commitdda1fc81be620375eebca33ef53a1eff2eb2bb51 (patch)
treeb7ace2dd96b0b2b0326a93881c163c96362b5c0e /.travis.yml
parent53a42e6268bca45c42c54aba3ee70c433a58dc83 (diff)
downloadsystemd-dda1fc81be620375eebca33ef53a1eff2eb2bb51.tar.gz
travis: run Coverity after Fuzzit-Fuzzing
Coverity is unpredictable and, according to a notification I received yeserday, it will be upgraded on June 17. During the upgrade it might be offline for 3 days, af far as I understand. Anyway, Travis stops as soon as a stage fails so it makes sense to put stages that are likely to fail at the end so that the others have a chance to do what they are supposed to do. https://community.synopsys.com/s/topic/0TO2H0000001CN7WAM/coverity-scan-status
Diffstat (limited to '.travis.yml')
-rw-r--r--.travis.yml6
1 files changed, 3 insertions, 3 deletions
diff --git a/.travis.yml b/.travis.yml
index 864d84f170..f41b43ed22 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -11,11 +11,11 @@ env:
- REPO_ROOT="$TRAVIS_BUILD_DIR"
stages:
- # Run Coverity periodically instead of for each commit/PR
- - name: Coverity
+ - name: Fuzzit-Fuzzing
if: type = cron
- - name: Fuzzit-Fuzzing
+ # Run Coverity periodically instead of for each commit/PR
+ - name: Coverity
if: type = cron
jobs: