-
Bug
-
Resolution: Unresolved
-
Major
-
Jenkins ver. 1.466.2
Klocwork Plugin 1.14
Jenknis Host Server, Red Hat 4.4.6-4
Slave: Windows 7
Klocwork Server 9.5 SR1
The reporting part of this plugin is really attractive and easy to understand.
Since I need to setup both klocwork plug in both win and linux node, I need to maintain the "kwbuildproj" in my own ant script.
So I setup a free-style job to trigger my ant build. The ant build will handle all klocwork related commands, "kwadmin", "kwinject", "kwbuildproject" and "kwinspectreport".
After the ant script is done, a klocwork-result.xml is produced. The "Post-build Actions: Publish Klocwork test result report" capture the xml and show the report nicely on the build page. But after restart of Jenkins service, all the successful build of the job will be lost.
I guess (without evidence), there is some persistent structure has to be created in Jenkins build record to store the Klocwork report. Somehow, this structure doesn't get created with only executing the "Post build action".
[JENKINS-16026] Success build record lose after restart of Jenkins service
reeve lau
created issue -
reeve lau
made changes -
| Summary | Original: Success build record lose after restart restart or Jenkins service | New: Success build record lose after restart of Jenkins service |
reeve lau
made changes -
| Description |
Original:
The reporting part of this plugin is really attractive and easy to understand. Since I need to setup both klocwork plug in both win and linux node, I need to maintain the "kwbuildproj" in my own ant script. So I setup a free-style job to trigger my ant build. The ant build will handle all klocwork related commands, "kwadmin", "kwinject", "kwbuildproject" and "kwinspectreport". After the ant script is done, a klocwork-result.xml is produced. The "Post-build Actions: Publish Klocwork test result report" capture the xml and show the report nicely on the build page. But after restart of Jenkins service, all the successful build of the job will be lost. I guess (without evident), there is some persistent structure has to be created in Jenkins build record to store the Klocwork report. Somehow, this structure doesn't get created with only executing the "Post build action". |
New:
The reporting part of this plugin is really attractive and easy to understand. Since I need to setup both klocwork plug in both win and linux node, I need to maintain the "kwbuildproj" in my own ant script. So I setup a free-style job to trigger my ant build. The ant build will handle all klocwork related commands, "kwadmin", "kwinject", "kwbuildproject" and "kwinspectreport". After the ant script is done, a klocwork-result.xml is produced. The "Post-build Actions: Publish Klocwork test result report" capture the xml and show the report nicely on the build page. But after restart of Jenkins service, all the successful build of the job will be lost. I guess (without evidence), there is some persistent structure has to be created in Jenkins build record to store the Klocwork report. Somehow, this structure doesn't get created with only executing the "Post build action". |
| Workflow | Original: JNJira [ 146828 ] | New: JNJira + In-Review [ 176727 ] |
Same effect here with Jenkins 1.480.3, Klocwork plugin 1.14.1 on Windows XP 32bit SP3.
When we restart the Jenkins server, the successful Klocwork builds disappear.