summaryrefslogtreecommitdiffstats
path: root/shell/maven-coverity.sh
AgeCommit message (Collapse)AuthorFilesLines
2019-08-12Add a workaround to suppress specified files from Coverity Scan analysisArtem Naluzhnyy1-8/+29
Re-implement temporary(?) non-functional filter to ignore specific source code parts by Coverity Scan using "--fs-capture-search-exclude-regex" CLI parameter of "cov-build" tool. This functionality is important to filter out e.g. node_modules or src/tests. Instead we can remove all specified files after we got local build results but before we send them to Coverity server. Issue-ID: CIMAN-260 Signed-off-by: Artem Naluzhnyy <A.Naluzhnyy@samsung.com> Change-Id: I1175b593966a8b8732aa3f6841e9c450766de752
2019-08-01Add more attempts to submits Coverity Scan resultsArtem Naluzhnyy1-12/+33
Since the build process takes a lot of time and resources on our Jenkins executors it had better try to resubmit our results to Coverity Scan server if it replies with non-200 HTTP response. Issue-ID: CIMAN-260 Signed-off-by: Artem Naluzhnyy <A.Naluzhnyy@samsung.com> Change-Id: I8fd24d9f4f6181ff6e0817914ac649a140706b7e
2019-07-01Add static code analysis support for JavaScript/Python/Ruby/PHP.Artem Naluzhnyy1-1/+21
Two JJB project parameters have been introduced: * 'coverity-search-paths' - space separated list of paths that contain source code to analyse; * 'coverity-search-exclude-regexs' - space separated list of file name regexps to exclude from analysis. Example: project: name: 'sdc-coverity' jobs: - onap-gerrit-maven-coverity ... coverity-search-paths: 'catalog-ui/src/ openecomp-ui/src/ dox-sequence-diagram-ui/src' coverity-search-exclude-regexs: '/node_modules/' Issue-ID: CIMAN-260 Signed-off-by: Artem Naluzhnyy <A.Naluzhnyy@samsung.com> Change-Id: I8050a75a731c893ec2173f66d2e881fcc0877ed0
2019-06-27Archive Coverity analysed files list to the logs serverArtem Naluzhnyy1-0/+10
The list is stored in "cov-int/coverity-scan-analysed-files.log". Issue-ID: CIMAN-260 Signed-off-by: Artem Naluzhnyy <A.Naluzhnyy@samsung.com> Change-Id: Id27cb466977e0bd11e004fd819f66697ca16c26b
2019-06-12Validate downloaded Coverity tool checksumArtem Naluzhnyy1-0/+14
Issue-ID: CIMAN-260 Signed-off-by: Artem Naluzhnyy <A.Naluzhnyy@samsung.com> Change-Id: I73dae5c4c5bd3dd73957809b4265009b529ebca0
2019-06-12Check Coverity service API usage quotaArtem Naluzhnyy1-0/+25
Check if we are allowed to submit results to Coverity Scan service and have not exceeded our upload quota limits. See also: https://scan.coverity.com/faq#frequency Issue-ID: CIMAN-260 Signed-off-by: Artem Naluzhnyy <A.Naluzhnyy@samsung.com> Change-Id: I71479cfdd8403e717e6c807a8afb5aadad25fdde
2019-06-10Add JJB template for static code analysis by Coverity Scan serviceArtem Naluzhnyy1-0/+97
"onap-gerrit-maven-coverity" JJB template runs 'mvn clean install' and then publishes results to Coverity Scan service for static code analysis. Usage example: - project: name: so-coverity jobs: - onap-gerrit-maven-coverity cron: '@daily' build-node: 'ubuntu1604-builder-4c-4g' project: 'so' project-name: 'so' branch: 'master' mvn-settings: 'so-settings' mvn-goals: 'clean install' mvn-opts: '-Xmx1024m -XX:MaxPermSize=256m' mvn-params: '-Dmaven.test.skip=true' coverity-project-name: 'onap-so' coverity-token: 'PUT COVERITY TOKEN HERE' coverity-user-email: 'PUT USER EMAIL HERE' Issue-ID: CIMAN-260 Signed-off-by: Artem Naluzhnyy <A.Naluzhnyy@samsung.com> Change-Id: I6f4fa6359b5be91932c5a1a1ed7ba0a4068ac152