Fix dcc213d ('max-git-repo-age-hours' behaviour) 01/96401/1
authorArtem Naluzhnyy <A.Naluzhnyy@samsung.com>
Mon, 30 Sep 2019 08:00:50 +0000 (10:00 +0200)
committerArtem Naluzhnyy <A.Naluzhnyy@samsung.com>
Mon, 30 Sep 2019 08:00:50 +0000 (10:00 +0200)
Issue-ID: CIMAN-260
Signed-off-by: Artem Naluzhnyy <A.Naluzhnyy@samsung.com>
Change-Id: I6b02c57f03b6b8ff9576924e712ed517225822de

shell/maven-coverity.sh

index 3361d40..eed10c4 100644 (file)
@@ -37,7 +37,7 @@ fi
 if [ ${MAX_GIT_REPO_AGE_HOURS:=0} -ne 0 ]; then
   LAST_COMMIT_AGE=$(( $(date +%s) - $(git log -1 --pretty=format:%ct) ))
 
-  if [ $LAST_COMMIT_AGE -le $(( MAX_GIT_REPO_AGE_HOURS *60*60 )) ]; then
+  if [ $LAST_COMMIT_AGE -gt $(( MAX_GIT_REPO_AGE_HOURS *60*60 )) ]; then
     echo '[NOTICE] Git repository did not have any commits last' \
       "${MAX_GIT_REPO_AGE_HOURS} hours - no need to re-analyse it." \
       >&2