[JIRA] (JENKINS-13411) Klocwork XML output is deprecated
M S commented on JENKINS-13411 Klocwork XML output is deprecated Would it be possible that the plugin will still allow xml parsing for Klocwork 9.6+? But with a different schema validation? Using http://developer.klocwork.com/community/forums/klocwork-general/web-api/webapi-issue-export-python-script with some changes we can obtain xml parseable for Jenkins and in the end have nice charts displayed in Jenkins. However due to lack of information about faulty lines in json form webapi (no column, line, prefix, postfix, trace etc) I had to put many fake tags in the xml, to get it parsed. 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
[JIRA] (JENKINS-14455) [cppcheck] Wrong job status set based on new errors treshold
M S commented on JENKINS-14455 [cppcheck] Wrong job status set based on new errors treshold I will check it with cppcheck plugin version 1.10 (I didn't notice it yesterday) and if the problem still occurs I will attach the config.xml 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
[JIRA] (JENKINS-14455) [cppcheck] Wrong job status set based on new errors treshold
M S resolved JENKINS-14455 as Fixed [cppcheck] Wrong job status set based on new errors treshold Problem doesn't appear anymore in cppcheck plugin version 1.10 Change By: M S (19/Jul/12 10:52 AM) Status: InProgress Resolved Fix Version/s: current Resolution: Fixed 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
[JIRA] (JENKINS-14455) [cppcheck] Wrong job status set based on new errors treshold
M S created JENKINS-14455 [cppcheck] Wrong job status set based on new errors treshold Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: cppcheck Created: 17/Jul/12 8:21 AM Description: Even though CppCheck results page from the analyzis doesn't show new errors (and the sum of errors doesn't change between 2 runs), in the console output of the job we can see that it sets build as unstable as new errors were found. Cppcheck Setting build status to UNSTABLE since total number of new errors (With all severity values) exceeds the threshold value '1'. Cppcheck Ending the cppcheck analysis. Severity Error (nb/new) : 46/+0 Severity Warning (nb/new) : 2405/+0 Severity Style (nb/new) : 1736/+0 Severity Performance (nb/new) : 1506/+0 Severity Information (nb/new) : 0/+0 Severity Unknown (nb/new) : 11/0 Environment: Linux, cppcheck version 1.55, jenkins 1.471, cppcheck plugin 1.9 Project: Jenkins Priority: Major Reporter: M S 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
[JIRA] (JENKINS-13429) Nested views not showing up with just read perms for View
M S created JENKINS-13429: - Summary: Nested views not showing up with just read perms for View Key: JENKINS-13429 URL: https://issues.jenkins-ci.org/browse/JENKINS-13429 Project: Jenkins Issue Type: Bug Components: nested-view Affects Versions: current Reporter: M S Assignee: Alan Harder Jenkins 1.459 + Nested View Plugin 1.8 + Role-based Authorization Strategy 1.1.2 User has read permissions for View but Jenkins main page is missing Nested views (even if they have sub views with jobs). Adding configure perms for View results in Nested views showing up correctly. It looks like it's connected with: Added the View.READ permission to control visibility of views, and updated the default implementation to hide empty views. (issue 3681) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
