diff options
| author | Patrick Steinhardt <ps@pks.im> | 2016-10-28 14:48:30 +0200 |
|---|---|---|
| committer | Patrick Steinhardt <ps@pks.im> | 2016-10-28 14:56:10 +0200 |
| commit | 561276eed6be2c763af23ae3b034a1f194b03d0b (patch) | |
| tree | 2b636478806f894024e738011767ca2e80d6a5f4 /script | |
| parent | 6c4d2d3ea208bfd0d38d7c5071ea0b398e71c5c8 (diff) | |
| download | libgit2-561276eed6be2c763af23ae3b034a1f194b03d0b.tar.gz | |
coverity: only analyze the master branch of the main repository
We used to only execute Coverity analysis on the 'development'
branch before commit 998f001 (Refine build limitation,
2014-01-15), which refined Coverity build limitations. While we
do not really use the 'development' branch anymore, it does
still make sense to only analyze a single branch, as otherwise
Coverity might get confused.
Re-establish the restriction such that we only analyze libgit2's
'master' branch. Also fix the message announcing why we do not
actually analyze a certain build.
Diffstat (limited to 'script')
| -rwxr-xr-x | script/coverity.sh | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/script/coverity.sh b/script/coverity.sh index 229a9c370..9021b9e7c 100755 --- a/script/coverity.sh +++ b/script/coverity.sh @@ -5,10 +5,10 @@ set -e [ -z "$COVERITY_TOKEN" ] && echo "Need to set a coverity token" && exit 1 # Only run this on our branches -echo "Pull request: $TRAVIS_PULL_REQUEST | Slug: $TRAVIS_REPO_SLUG" -if [ "$TRAVIS_PULL_REQUEST" != "false" -o "$TRAVIS_REPO_SLUG" != "libgit2/libgit2" ]; +echo "Branch: $TRAVIS_BRANCH | Pull request: $TRAVIS_PULL_REQUEST | Slug: $TRAVIS_REPO_SLUG" +if [ "$TRAVIS_BRANCH" != "master" -o "$TRAVIS_PULL_REQUEST" != "false" -o "$TRAVIS_REPO_SLUG" != "libgit2/libgit2" ]; then - echo "Only analyzing 'development' on the main repo." + echo "Only analyzing the 'master' brach of the main repository." exit 0 fi |