summaryrefslogtreecommitdiffstats
path: root/jjb/ci-management
diff options
context:
space:
mode:
authorArtem Naluzhnyy <A.Naluzhnyy@samsung.com>2019-09-02 14:27:36 +0200
committerArtem Naluzhnyy <a.naluzhnyy@samsung.com>2019-09-03 09:43:32 +0000
commitdcc213dedc51a82832f90d644f14b28a3e55aa18 (patch)
tree1f5f90bb2013b954a5a7af3197f73e451324699c /jjb/ci-management
parent5b0faffcb99bb520786c45d9f58d83a094dcf7b1 (diff)
Add workaround for broken git repo polling by Jenkins
To save our Jenkins lab resources and Coverity Scan submission quota we can run the scan if there were recent commits only. At the moment the following JJB configuration does not work properly for ONAP repositories: triggers: - pollscm: cron: '@daily' As a workaround a new job build parameter is introduced - 'max-git-repo-age-hours'. If set to non-zero run the code scan only if there were no git repository commits last max-git-repo-age-hours hours. It makes sense to set the value twice the 'cron' interval for the job (e.g. if 'cron: @daily', then max-git-repo-age-hours=48). Issue-ID: CIMAN-260 Signed-off-by: Artem Naluzhnyy <A.Naluzhnyy@samsung.com> Change-Id: I82ce092e9b8bb423e9db8b3958d6cfa3b527b33b
Diffstat (limited to 'jjb/ci-management')
-rw-r--r--jjb/ci-management/ci-management-coverity.yaml9
1 files changed, 9 insertions, 0 deletions
diff --git a/jjb/ci-management/ci-management-coverity.yaml b/jjb/ci-management/ci-management-coverity.yaml
index fadea8882..6003bf24e 100644
--- a/jjb/ci-management/ci-management-coverity.yaml
+++ b/jjb/ci-management/ci-management-coverity.yaml
@@ -41,6 +41,7 @@
coverity-user-email: ''
coverity-search-paths: ''
coverity-search-exclude-regexs: ''
+ max-git-repo-age-hours: 0
stream: master
submodule-recursive: true
submodule-timeout: 10
@@ -101,6 +102,14 @@
name: DRY_RUN
default: '{dry-run}'
description: Do not submit results to Coverity Scan server at the end of the build.
+ - string:
+ name: 'MAX_GIT_REPO_AGE_HOURS'
+ default: '{max-git-repo-age-hours}'
+ description: >
+ If set to non-zero run the code scan only if there were no git
+ repository commits last MAX_GIT_REPO_AGE_HOURS hours.
+ It makes sense to set the value twice the 'cron' interval for the
+ job (e.g. if 'cron: @daily', then MAX_GIT_REPO_AGE_HOURS=48)
triggers:
- timed: '{obj:cron}'