![]() |
|
|
|
|
Change By:
|
Martin Hohl
(05/Nov/14 6:02 PM)
|
|
Description:
|
Unexpected behavior of Integrity plugin after message "A SQL Exception was caught! Table/View 'CM_PROJECT' does not exist.":
The Integrity - CM Polling Log says
"Started on Nov 5, 2014 7:00:00 AM
Preparing to execute si projectinfo for #p=p:/PROJEKTE/2230/2230.pj#s=Software/Software.pj#s=PC/PC.pj#s=StLib/StLib.pj
Preparing to execute si viewproject for #p=p:/PROJEKTE/2230/2230.pj#s=Software/Software.pj#s=PC/PC.pj#s=StLib/StLib.pj
A SQL Exception was caught!
Table/View 'CM_PROJECT' does not exist.
Done. Took 7.8 sec
No changes"
and the job status of the build job is not FAILED
, but "Finished: SUCCESS"
.
Normally, if the plugin says "Failed to establish an API connection to the Integrity Server!" it fails the build job (as expected).
I would not expect that a Jenkins job can have status OK, if the workspace cannot be populated or updated with the SCM configured for that job.
The issue occurred the first time after an upgrade of the Integrity plugin (previous version was 1.24, current version is 1.28). Without administrator intervention the "pseudo-good" builds with outdated workspace contents were consistenly occurring since that moment...
|
|
|
|
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.
