![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Ken Dang
|
|
Components:
|
coverity-plugin |
|
Created:
|
03/Dec/14 11:27 AM
|
|
Description:
|
Post-build action Coverity has an option called "Perform Coverity build, analysis and commit". The documentation says that when enabling it, the plugin will monitor the build with cov-build and trigger analyse and commit automatically. If not enabled, the build script has to do it itself.
Unfortunately, regardless if the option is enabled or disabled, the build script is invoked through cov-build. This conflicts with the documentation.
The undesired effect is that the coverity config needs to be provided externally to the build as it needs to be available when cov-build is starting, so before the build script is triggered. This is undesirable as it prevents the job definition from being self contained. Also, as - in my case - it is the build that decides on what compiler and in what versions to use, so I would prefer to set up the coverity config on every build from inside the script.
|
|
Environment:
|
jenkins - 1.581
coverity plugin - 1.4.1
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Michal Ejdys
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
