Skip to content

Commit 561276e

Browse files
pks-tpks-t
committed
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.
1 parent 6c4d2d3 commit 561276e

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

‎script/coverity.sh‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,10 +5,10 @@ set -e
55
[ -z "$COVERITY_TOKEN" ] && echo "Need to set a coverity token" && exit 1
66

77
# Only run this on our branches
8-
echo "Pull request: $TRAVIS_PULL_REQUEST | Slug: $TRAVIS_REPO_SLUG"
9-
if [ "$TRAVIS_PULL_REQUEST" != "false" -o "$TRAVIS_REPO_SLUG" != "libgit2/libgit2" ];
8+
echo "Branch: $TRAVIS_BRANCH | Pull request: $TRAVIS_PULL_REQUEST | Slug: $TRAVIS_REPO_SLUG"
9+
if [ "$TRAVIS_BRANCH" != "master" -o "$TRAVIS_PULL_REQUEST" != "false" -o "$TRAVIS_REPO_SLUG" != "libgit2/libgit2" ];
1010
then
11-
echo "Only analyzing 'development' on the main repo."
11+
echo "Only analyzing the 'master' brach of the main repository."
1212
exit 0
1313
fi
1414

0 commit comments

Comments
 (0)