[JIRA] [sloccount-plugin] (JENKINS-31221) Get total comment count in SloccountReportStatistics
Title: Message Title Michal Turek closed an issue as Fixed Jenkins / JENKINS-31221 Get total comment count in SloccountReportStatistics Change By: Michal Turek Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [sloccount-plugin] (JENKINS-31221) Get total comment count in SloccountReportStatistics
Title: Message Title Michal Turek resolved as Fixed Released in version 1.21, it should appear in Update center in a day or so. Jenkins / JENKINS-31221 Get total comment count in SloccountReportStatistics Change By: Michal Turek Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [sloccount-plugin] (JENKINS-29216) SLOCCount plugin is not releasing log
Title: Message Title Michal Turek commented on JENKINS-29216 Re: SLOCCount plugin is not releasing log Hi, does the .nfs000xxx file contain output of SLOCCount executable (meaning /usr/bin/sloccount) or the Jenkins SLOCCount plugin? The plugin has nothing to do with the executable except it parses file generated by it. Can you further analyze the issue? Did you tried to use alternative cloc for generating of the report for example? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [disk-usage-plugin] (JENKINS-22721) Project page has broken layout on smaller screens
Michal Turek commented on JENKINS-22721 Project page has broken layout on smaller screens Hi, it's here https://github.com/jenkinsci/disk-usage-plugin/pull/20. 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.
[JIRA] [cppcheck] (JENKINS-24834) CPP check report background colours not displaying for new or resolved issues since upgrade
Michal Turek closed JENKINS-24834 as Fixed CPP check report background colours not displaying for new or resolved issues since upgrade Change By: Michal Turek (10/Oct/14 8:58 PM) Status: Resolved Closed 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.
[JIRA] [cppcheck] (JENKINS-24037) CPPCheck Plugin: You need worspace message instead of workspace
Michal Turek closed JENKINS-24037 as Fixed CPPCheck Plugin: You need worspace message instead of workspace Change By: Michal Turek (10/Oct/14 8:57 PM) Status: Resolved Closed 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.
[JIRA] [cppcheck] (JENKINS-23575) Post-Build-Step Publish Cppcheck results not available in job generator project
Michal Turek resolved JENKINS-23575 as Fixed Post-Build-Step Publish Cppcheck results not available in job generator project The issue is related to a particular version of Jenkins core together with quite old version of IE so I'm closing this task for Cppcheck plugin. Please open a new Jenkins core task if you want to continue with any investigation. Change By: Michal Turek (10/Oct/14 8:57 PM) Status: Reopened Resolved 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 -- 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.
[JIRA] [cppcheck] (JENKINS-23575) Post-Build-Step Publish Cppcheck results not available in job generator project
Michal Turek closed JENKINS-23575 as Fixed Post-Build-Step Publish Cppcheck results not available in job generator project Change By: Michal Turek (10/Oct/14 8:57 PM) Status: Resolved Closed 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.
[JIRA] [cppcheck] (JENKINS-24007) Put a warning about report in legacy format to build log
Michal Turek closed JENKINS-24007 as Fixed Put a warning about report in legacy format to build log Change By: Michal Turek (10/Oct/14 8:57 PM) Status: Resolved Closed 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.
[JIRA] [cppcheck] (JENKINS-23247) Display trends graph last 10/20 sucessful/fail builds in CPPcheck plugin.
Michal Turek closed JENKINS-23247 as Fixed Display trends graph last 10/20 sucessful/fail builds in CPPcheck plugin. Change By: Michal Turek (10/Oct/14 8:58 PM) Status: Resolved Closed 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.
[JIRA] [cppcheck] (JENKINS-24076) Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced)
Michal Turek commented on JENKINS-24076 Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced) Please see comments in your pull request, they should be solved before merge. https://github.com/jenkinsci/cppcheck-plugin/pull/24 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.
[JIRA] [cppcheck] (JENKINS-24834) CPP check report background colours not displaying for new or resolved issues since upgrade
Michal Turek started work on JENKINS-24834 CPP check report background colours not displaying for new or resolved issues since upgrade Change By: Michal Turek (27/Sep/14 7:14 PM) Status: Open InProgress 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.
[JIRA] [cppcheck] (JENKINS-24834) CPP check report background colours not displaying for new or resolved issues since upgrade
Michal Turek resolved JENKINS-24834 as Fixed CPP check report background colours not displaying for new or resolved issues since upgrade Fixed, will be released in version 1.20. Change By: Michal Turek (27/Sep/14 7:30 PM) Status: InProgress Resolved Assignee: GregoryBoissinot MichalTurek 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 -- 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.
[JIRA] [cppcheck] (JENKINS-23247) Display trends graph last 10/20 sucessful/fail builds in CPPcheck plugin.
Michal Turek started work on JENKINS-23247 Display trends graph last 10/20 sucessful/fail builds in CPPcheck plugin. Change By: Michal Turek (27/Sep/14 8:36 PM) Status: Open InProgress 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.
[JIRA] [cppcheck] (JENKINS-23247) Display trends graph last 10/20 sucessful/fail builds in CPPcheck plugin.
Michal Turek resolved JENKINS-23247 as Fixed Display trends graph last 10/20 sucessful/fail builds in CPPcheck plugin. Implemented, will be released in version 1.20. Change By: Michal Turek (27/Sep/14 9:07 PM) Status: InProgress Resolved 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 -- 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.
[JIRA] [cppcheck] (JENKINS-23575) Post-Build-Step Publish Cppcheck results not available in job generator project
Michal Turek commented on JENKINS-23575 Post-Build-Step Publish Cppcheck results not available in job generator project This is strange. Is the own build from the same sources and without any change (like different version of parent in Maven) and running under the same version of Jenkins in the same environment? I'm looking at JENKINS-14491 and JENKINS-14514, did you notice any error in Jenkins log or _javascript_ console (if IE has anything like this) after clicking the button? As I said this looks more like Jenkins core issue than issue of this plugin, I'm only returning a string with "Publish Cppcheck results" in getDisplayName(). I have neither IE nor Windows so debugging from my side is impossible. 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.
[JIRA] [cppcheck] (JENKINS-23247) Display trends graph last 10/20 sucessful/fail builds in CPPcheck plugin.
Michal Turek commented on JENKINS-23247 Display trends graph last 10/20 sucessful/fail builds in CPPcheck plugin. Hi, I'm not interested in this feature and I have nearly no free time so I don't expect any work on this task from my side, sorry. But anyone can implement it and send a pull request... 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.
[JIRA] [cppcheck] (JENKINS-23575) Post-Build-Step Publish Cppcheck results not available in job generator project
Michal Turek commented on JENKINS-23575 Post-Build-Step Publish Cppcheck results not available in job generator project Hi Lukas, I have just tried to reproduce your issue, but it works for me with Jenkins 1.578, Cppcheck plugin 1.19, Job Generator plugin 1.22 and 64-bit Linux version of Chrome 37. I executed Jenkins using the command below and manually installed the plugins using the update center. mkdir -p home export JENKINS_HOME=home java -jar jenkins.war I created Job Generator job template, added Cppcheck publisher there and configured it. Then I generated a new job using the generator, executed a built and verified the published Cppcheck data are available. I guess if there is any issue it will be in some _javascript_ that comes directly from Jenkins. The plugin only provides a string to display in this menu, the real adding of publisher is done by Jenkins itself. Did you try to refresh the configuration page and try again? Did you try to add a different publisher using the same menu? Did you try a different web browser? Can you verify the issue is still present in the latest versions? M. 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.
[JIRA] [cppcheck] (JENKINS-24076) Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced)
Michal Turek stopped work on JENKINS-24076 Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced) Change By: Michal Turek (10/Sep/14 6:45 PM) Status: InProgress Open 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.
[JIRA] [cppcheck] (JENKINS-24076) Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced)
Michal Turek commented on JENKINS-24076 Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced) I understand WHAT you want but I don't understand WHY you want it. Your usage patter is from the very special ones. As I understand you have a set of issues reported by Cppcheck, let's say 100 of them, which you want to just ignore and never fix. So you set a threshold to make the build unstable if there is more than 100 issues. And you want to update the plugin to see all issues that don't belong to the 100 known ones in the latest build. You are also dropping the history off time to time so you are not sure which issues were the 100 original ones, but you know there were 100 of them. Correct? My suggestion was to analyze that 100 issues and use --inline-suppr, --suppress or --suppressions-list cppcheck arguments to hide them. Cppcheck would report no issues instead of 100 now and any issue present in the latest build would be in "to fix" category. Does it make sense? Questions: What should happen in your proposal if unit tests (or whatever else) make the build unstable instead of Cppcheck? What to do with the missing history containing the last stable build, do you plan to change data model to store the deltas too? If somebody fixes one of the 100 original issues by happy accident, the threshold should be updated to 99. Newly introduced issue may be a serious memory leak or whatever but the build will be still reported as stable and the "delta with last stable build" approach will seriously fail. Feel free to create a feature branch for this task and send a pull request. That's just my two cents. 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.
[JIRA] [cppcheck] (JENKINS-24076) Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced)
Michal Turek updated JENKINS-24076 Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced) Change By: Michal Turek (10/Sep/14 6:47 PM) Issue Type: Bug NewFeature Priority: Critical Major 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.
[JIRA] [cppcheck] (JENKINS-24076) Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced)
Michal Turek assigned JENKINS-24076 to Craig Phillips Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced) Change By: Michal Turek (10/Sep/14 6:46 PM) Assignee: MichalTurek CraigPhillips 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.
[JIRA] [cppcheck] (JENKINS-24076) Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced)
Michal Turek edited a comment on JENKINS-24076 Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced) I understand WHAT you want but I don't understand WHY you want it. Your usage patter is from the very special ones. As I understand you have a set of issues reported by Cppcheck, let's say 100 of them, which you want to just ignore and never fix. So you set a threshold to make the build unstable if there is more than 100 issues. And you want to update the plugin to see all issues that don't belong to the 100 known ones in the latest build. You are also dropping the history off time to time so you are not sure which issues were the 100 original ones, but you know there were 100 of them. Correct? My suggestion was to analyze that 100 issues and use --inline-suppr, --suppress or --suppressions-list cppcheck arguments to hide them. Cppcheck would report no issues instead of 100 now and any issue present in the latest build would belong to the "to fix" category. Does it make sense? Surely, feel free to create a feature branch for this task and send a pull request. Questions: What should happen in your proposal if unit tests (or whatever else) make the build unstable instead of Cppcheck? What to do with the missing history containing the last stable build, do you plan to change data model to store the deltas too? If somebody fixes one of the 100 original issues by happy accident, the threshold should be updated to 99. Newly introduced issue may be a serious memory leak or whatever but the build will be still reported as stable and the "delta with last stable build" approach will seriously fail. That's just my two cents. 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.
[JIRA] [cppcheck] (JENKINS-24076) Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced)
Michal Turek started work on JENKINS-24076 Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced) Change By: Michal Turek (07/Sep/14 5:05 PM) Status: Open InProgress 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.
[JIRA] [cppcheck] (JENKINS-24076) Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced)
Michal Turek commented on JENKINS-24076 Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced) Hi Craig, I read all of the comments several times and I think you misunderstood the behavior of the plugin a lot. Actually it's much simpler than you expect. All builds are independent, they share no data. Each build stores only the data that were generated during its run. If you delete a build (or let Jenkins to delete it), all of its data will be lost so the plugin will be unable to use them. Prolong the history to store more builds or to store them for longer time if you need them. Delta is computed dynamically while presenting the results. The currently displayed build and the previous one is used (N and N-1 if exists). It is for example build 50 and 49. If you delete 49 then build 50 and 48 will be used. This can be changed to go deeper in the history and skip builds with no Cppcheck data, e.g. the failed ones. The plugin doesn't consider last stable build, last unstable build, etc. at all. It is surely possible to have zero delta together with non-zero count of new/solved issue. For example if 5 style issues are solved and 5 new ones introduced, the delta will be zero. Unfortunatelly I can't determine if this is the case, the screenshot is incomplete. Did you consider to use any of these Cppcheck options? I guess they can help you a lot. --inline-suppr Enable inline suppressions. Use them by placing comments in the form: // cppcheck-suppress memleak before the line to suppress. --suppress=spec Suppress a specific warning. The format of spec is: [error id]:[filename]:[line]. The [filename] and [line] are optional. [error id] may be * to suppress all warnings (for a specified file or files). [filename] may contain the wildcard characters * or ?. --suppressions-list=file Suppress warnings listed in the file. Each suppression is in the format of spec above. 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.
[JIRA] [sloccount] (JENKINS-24602) Native support for cloc tool
Michal Turek started work on JENKINS-24602 Native support for cloc tool Change By: Michal Turek (06/Sep/14 9:58 AM) Status: Open InProgress 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.
[JIRA] [sloccount] (JENKINS-24602) Native support for cloc tool
Michal Turek resolved JENKINS-24602 as Fixed Native support for cloc tool Implemented, will be released in version 1.20. Change By: Michal Turek (06/Sep/14 9:59 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 -- 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.
[JIRA] [sloccount] (JENKINS-21922) Remote access API (REST API)
Michal Turek closed JENKINS-21922 as Fixed Remote access API (REST API) Change By: Michal Turek (06/Sep/14 10:02 AM) Status: Resolved Closed 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.
[JIRA] [sloccount] (JENKINS-24602) Native support for cloc tool
Michal Turek created JENKINS-24602 Native support for cloc tool Issue Type: New Feature Affects Versions: current Assignee: Michal Turek Components: sloccount Created: 05/Sep/14 3:46 PM Description: Cloc is supported only by explicit XML transformation to SLOCCount file format at the moment. It would be useful to read cloc file format directly in the plugin code. Cloc is able to detect more languages than SLOCCount (Scala, Ant, ...) and counts also lines with comments that often contain Javadoc or Doxygen documentation. Environment: all Project: Jenkins Priority: Major Reporter: Michal Turek 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.
[JIRA] [cppcheck] (JENKINS-24076) Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced)
Michal Turek commented on JENKINS-24076 Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced) Hi, I will look at the issue, but I have no time for that at the moment. If you are really desperate, you can debug and fix the issue by yourself and create a pull request. The related code is org.jenkinsci.plugins.cppcheck.CppcheckResult.getDiff() for summary and diffCurrentAndPrevious() for details. Data of previous build comes from getPreviousResult(), I guess there should be loop to the builds history instead of single if condition. I have updated similar code in sloccount plugin, it may be the same. The report is initially parsed and stored in org.jenkinsci.plugins.cppcheck.CppcheckPublisher.perform(). Hope this will help for quick orientation in the code... 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.
[JIRA] [sloccount] (JENKINS-24093) Clean jelly code
Michal Turek started work on JENKINS-24093 Clean jelly code Change By: Michal Turek (03/Aug/14 3:31 PM) Status: Open InProgress 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.
[JIRA] [sloccount] (JENKINS-24093) Clean jelly code
Michal Turek created JENKINS-24093 Clean jelly code Issue Type: Task Affects Versions: current Assignee: Michal Turek Components: sloccount Created: 03/Aug/14 3:31 PM Description: There are some errors and warnings reported by IDE in jelly files, solve them. Environment: all Project: Jenkins Priority: Minor Reporter: Michal Turek 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.
[JIRA] [sloccount] (JENKINS-24093) Clean jelly code
Michal Turek resolved JENKINS-24093 as Fixed Clean jelly code Version 1.20. Change By: Michal Turek (03/Aug/14 4:28 PM) 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 -- 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.
[JIRA] [sloccount] (JENKINS-24094) Folding help in configuration
Michal Turek created JENKINS-24094 Folding help in configuration Issue Type: Improvement Affects Versions: current Assignee: Michal Turek Components: sloccount Created: 03/Aug/14 5:13 PM Description: Update the configuration page to use folding help for all fields instead of long hard coded texts. Environment: all Project: Jenkins Priority: Minor Reporter: Michal Turek 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.
[JIRA] [sloccount] (JENKINS-24094) Folding help in configuration
Michal Turek resolved JENKINS-24094 as Fixed Folding help in configuration Implemented, will be released in version 1.20. Change By: Michal Turek (03/Aug/14 5:43 PM) 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 -- 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.
[JIRA] [sloccount] (JENKINS-24094) Folding help in configuration
Michal Turek started work on JENKINS-24094 Folding help in configuration Change By: Michal Turek (03/Aug/14 5:42 PM) Status: Open InProgress 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.
[JIRA] [cppcheck] (JENKINS-24037) CPPCheck Plugin: You need worspace message instead of workspace
Michal Turek assigned JENKINS-24037 to Michal Turek CPPCheck Plugin: You need worspace message instead of workspace Change By: Michal Turek (03/Aug/14 5:50 PM) Assignee: GregoryBoissinot MichalTurek 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.
[JIRA] [cppcheck] (JENKINS-24037) CPPCheck Plugin: You need worspace message instead of workspace
Michal Turek started work on JENKINS-24037 CPPCheck Plugin: You need worspace message instead of workspace Change By: Michal Turek (03/Aug/14 5:50 PM) Status: Open InProgress 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.
[JIRA] [cppcheck] (JENKINS-24037) CPPCheck Plugin: You need worspace message instead of workspace
Michal Turek resolved JENKINS-24037 as Fixed CPPCheck Plugin: You need worspace message instead of workspace Fixed, will be released in version 1.20. Change By: Michal Turek (03/Aug/14 5:54 PM) 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 -- 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.
[JIRA] [sloccount] (JENKINS-24021) Show statistics from last build on main job page
Michal Turek created JENKINS-24021 Show statistics from last build on main job page Issue Type: Improvement Affects Versions: current Assignee: Michal Turek Components: sloccount Created: 29/Jul/14 7:45 PM Description: Show the same table with statistics from last SloccountBuildAction in SloccountProjectAction page. Environment: all Project: Jenkins Priority: Major Reporter: Michal Turek 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.
[JIRA] [sloccount] (JENKINS-24021) Show statistics from last build on main job page
Michal Turek updated JENKINS-24021 Show statistics from last build on main job page Change By: Michal Turek (29/Jul/14 7:54 PM) Description: ShowthesametablewithstatisticsfromlastSloccountBuildActioninSloccountProjectActionpage. SimilartaskinCppcheckpluginisJENKINS-22388. 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.
[JIRA] [sloccount] (JENKINS-24021) Show statistics from last build on main job page
Michal Turek updated JENKINS-24021 Show statistics from last build on main job page Change By: Michal Turek (29/Jul/14 7:56 PM) Attachment: project_action.png 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.
[JIRA] [sloccount] (JENKINS-24021) Show statistics from last build on main job page
Michal Turek resolved JENKINS-24021 as Fixed Show statistics from last build on main job page Implemented, will be released in version 1.20. Change By: Michal Turek (29/Jul/14 7:57 PM) Status: Open 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 -- 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.
[JIRA] [cppcheck] (JENKINS-23185) Setting build status to FAILURE for new error when errors were fixed
Michal Turek commented on JENKINS-23185 Setting build status to FAILURE for new error when errors were fixed You are welcome 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.
[JIRA] [cppcheck] (JENKINS-24007) Put a warning about report in legacy format to build log
Michal Turek created JENKINS-24007 Put a warning about report in legacy format to build log Issue Type: New Feature Affects Versions: current Assignee: Michal Turek Components: cppcheck Created: 28/Jul/14 7:06 PM Description: If '--xml-version=2' is not passed to Cppcheck, it will generate the report in legacy format. Build log should contain a warning about that to inform the user. --xml Write results in XML to error stream --xml-version=version Select the XML file version. Currently versions 1 and 2 are available. The default version is 1. Environment: All Project: Jenkins Priority: Trivial Reporter: Michal Turek 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.
[JIRA] [cppcheck] (JENKINS-17450) warning and performance not counted
Michal Turek commented on JENKINS-17450 warning and performance not counted Simple but great idea, JENKINS-24007 created, thanks 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.
[JIRA] [cppcheck] (JENKINS-23891) Redesign of configuration page
Michal Turek closed JENKINS-23891 as Fixed Redesign of configuration page Change By: Michal Turek (28/Jul/14 7:18 PM) Status: Resolved Closed 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.
[JIRA] [cppcheck] (JENKINS-23185) Setting build status to FAILURE for new error when errors were fixed
Michal Turek closed JENKINS-23185 as Fixed Setting build status to FAILURE for new error when errors were fixed Change By: Michal Turek (28/Jul/14 7:18 PM) Status: Resolved Closed 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.
[JIRA] [cppcheck] (JENKINS-23575) Post-Build-Step Publish Cppcheck results not available in job generator project
Michal Turek closed JENKINS-23575 as Fixed Post-Build-Step Publish Cppcheck results not available in job generator project Change By: Michal Turek (28/Jul/14 7:18 PM) Status: Resolved Closed 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.
[JIRA] [cppcheck] (JENKINS-23888) Add query parameter support for filtering errors based on new, resolved or unchanged
Michal Turek closed JENKINS-23888 as Fixed Add query parameter support for filtering errors based on new, resolved or unchanged Change By: Michal Turek (28/Jul/14 7:18 PM) Status: Resolved Closed 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.
[JIRA] [cppcheck] (JENKINS-24007) Put a warning about report in legacy format to build log
Michal Turek resolved JENKINS-24007 as Fixed Put a warning about report in legacy format to build log Implemented, will be released in version 1.20. Change By: Michal Turek (28/Jul/14 7:22 PM) Status: Open 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 -- 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.
[JIRA] [cppcheck] (JENKINS-23185) Setting build status to FAILURE for new error when errors were fixed
Michal Turek resolved JENKINS-23185 as Fixed Setting build status to FAILURE for new error when errors were fixed Fixed, will be released in version 1.19. Change By: Michal Turek (27/Jul/14 2:49 PM) 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 -- 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.
[JIRA] [cppcheck] (JENKINS-23888) Add query parameter support for filtering errors based on new, resolved or unchanged
Michal Turek started work on JENKINS-23888 Add query parameter support for filtering errors based on new, resolved or unchanged Change By: Michal Turek (27/Jul/14 2:53 PM) Status: Open InProgress 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.
[JIRA] [cppcheck] (JENKINS-23888) Add query parameter support for filtering errors based on new, resolved or unchanged
Michal Turek assigned JENKINS-23888 to Michal Turek Add query parameter support for filtering errors based on new, resolved or unchanged Change By: Michal Turek (27/Jul/14 2:53 PM) Assignee: GregoryBoissinot MichalTurek 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.
[JIRA] [cppcheck] (JENKINS-23888) Add query parameter support for filtering errors based on new, resolved or unchanged
Michal Turek updated JENKINS-23888 Add query parameter support for filtering errors based on new, resolved or unchanged Change By: Michal Turek (27/Jul/14 5:16 PM) Attachment: state_filter.png 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.
[JIRA] [cppcheck] (JENKINS-23888) Add query parameter support for filtering errors based on new, resolved or unchanged
Michal Turek resolved JENKINS-23888 as Fixed Add query parameter support for filtering errors based on new, resolved or unchanged Implemented, will be released in version 1.19. Change By: Michal Turek (27/Jul/14 5:19 PM) 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 -- 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.
[JIRA] [cppcheck] (JENKINS-23891) Redesign of configuration page
Michal Turek updated JENKINS-23891 Redesign of configuration page Change By: Michal Turek (23/Jul/14 7:07 PM) Attachment: advanced.png Attachment: basic.png Attachment: helps.png 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.
[JIRA] [cppcheck] (JENKINS-23891) Redesign of configuration page
Michal Turek resolved JENKINS-23891 as Fixed Redesign of configuration page Implemented, will be released in version 1.19. Change By: Michal Turek (23/Jul/14 7:11 PM) 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 -- 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.
[JIRA] [cppcheck] (JENKINS-23185) Setting build status to FAILURE for new error when errors were fixed
Michal Turek started work on JENKINS-23185 Setting build status to FAILURE for new error when errors were fixed Change By: Michal Turek (23/Jul/14 7:16 PM) Status: Open InProgress 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.
[JIRA] [cppcheck] (JENKINS-23185) Setting build status to FAILURE for new error when errors were fixed
Michal Turek commented on JENKINS-23185 Setting build status to FAILURE for new error when errors were fixed I was referring to cppcheck manual page, e.g. http://linux.die.net/man/1/cppcheck, but it is not important now. I have updated the GUI under JENKINS-23891, it uses word "issue" instead of "error" now. 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.
[JIRA] [cppcheck] (JENKINS-23575) Post-Build-Step Publish Cppcheck results not available in job generator project
Michal Turek started work on JENKINS-23575 Post-Build-Step Publish Cppcheck results not available in job generator project Change By: Michal Turek (19/Jul/14 10:44 AM) Status: Open InProgress 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.
[JIRA] [cppcheck] (JENKINS-23575) Post-Build-Step Publish Cppcheck results not available in job generator project
Michal Turek assigned JENKINS-23575 to Michal Turek Post-Build-Step Publish Cppcheck results not available in job generator project Change By: Michal Turek (19/Jul/14 10:44 AM) Assignee: GregoryBoissinot MichalTurek 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.
[JIRA] [cppcheck] (JENKINS-23575) Post-Build-Step Publish Cppcheck results not available in job generator project
Michal Turek resolved JENKINS-23575 as Fixed Post-Build-Step Publish Cppcheck results not available in job generator project Implemented, will be released in version 1.19. Change By: Michal Turek (19/Jul/14 12:07 PM) 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 -- 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.
[JIRA] [cppcheck] (JENKINS-23247) Display trends graph last 10/20 sucessful/fail builds in CPPcheck plugin.
Michal Turek updated JENKINS-23247 Display trends graph last 10/20 sucessful/fail builds in CPPcheck plugin. Change By: Michal Turek (19/Jul/14 12:16 PM) Priority: Blocker Minor 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.
[JIRA] [cppcheck] (JENKINS-23247) Display trends graph last 10/20 sucessful/fail builds in CPPcheck plugin.
Michal Turek commented on JENKINS-23247 Display trends graph last 10/20 sucessful/fail builds in CPPcheck plugin. I have updated the priority from "Blocker" to "Minor". If I understand correctly, everything works as expected and this is only a feature request for showing only last N builds in the trend graph. 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.
[JIRA] [cppcheck] (JENKINS-23891) Redesign of configuration page
Michal Turek created JENKINS-23891 Redesign of configuration page Issue Type: Improvement Affects Versions: current Assignee: Michal Turek Components: cppcheck Created: 19/Jul/14 12:38 PM Description: Remove second "Advanced" button, update texts to be more understandable for new users, etc. Environment: all Project: Jenkins Priority: Major Reporter: Michal Turek 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.
[JIRA] [cppcheck] (JENKINS-23891) Redesign of configuration page
Michal Turek started work on JENKINS-23891 Redesign of configuration page Change By: Michal Turek (19/Jul/14 12:40 PM) Status: Open InProgress 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.
[JIRA] [cppcheck] (JENKINS-17450) warning and performance not counted
Michal Turek
commented on JENKINS-17450
warning and performance not counted
Oh, I understand now. Legacy XML v1 format uses severities that are not compatible with new XML v2. There is the following mapping in the plugin code.
if ("possible error".equals(cppcheckFile.getSeverity())) {
warningSeverityList.add(cppcheckFile);
} else if ("style".equals(cppcheckFile.getSeverity())) {
styleSeverityList.add(cppcheckFile);
} else if ("possible style".equals(cppcheckFile.getSeverity())) {
performanceSeverityList.add(cppcheckFile);
} else if ("error".equals(cppcheckFile.getSeverity())) {
errorSeverityList.add(cppcheckFile);
} else {
noCategorySeverityList.add(cppcheckFile);
}
allErrors.add(cppcheckFile);
You should always use XML v2. Cppcheck for example reports less issues with XML v1 than with XML v2 for the same analyzed code.
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.
[JIRA] [cppcheck] (JENKINS-17450) warning and performance not counted
Michal Turek resolved JENKINS-17450 as Wont Fix warning and performance not counted Rejected, the issue can't occur without manual modification of the input report. Change By: Michal Turek (11/Jul/14 6:16 PM) Status: Reopened Resolved Resolution: WontFix 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.
[JIRA] [cppcheck] (JENKINS-17450) warning and performance not counted
Michal Turek closed JENKINS-17450 as Wont Fix warning and performance not counted Change By: Michal Turek (11/Jul/14 6:17 PM) Status: Resolved Closed 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.
[JIRA] [cppcheck] (JENKINS-17450) warning and performance not counted
Michal Turek commented on JENKINS-17450 warning and performance not counted Hmmm, I'm absolutely unable to reproduce the issue, everything works for me. I tried the following: Debian testing, OpenJDK 7u55, Jenkins 1.447, latest git version of cppcheck plugin (~1.18), mvn hpi:run, cppcheck 1.61. New job with content of your config.xml from xml_extracts.txt. My own cppcheck-result.xml generated using "cppcheck --enable=all --inconclusive --xml --xml-version=2 graphal/graphal_gui 2 cppcheck-result.xml" that contains warning, style, performance and information severities. Content of generated files contains everything as expected and Jenkins presents the data correctly. Zipped job directory is attached as JENKINS-17450.tar.gz. New questions: What Java do you use (6/7/8, Oracle, OpenJDK, IBM, ...)? Please use "java -version" command. What version of cppcheck do you use? Please use "cppcheck --version" command. What command do you use to execute cppcheck and to generate the report passed to the plugin? Are you using XML version 2 as suggested at wiki? Are you sure all files in xml_extracts.txt belong to the same job/build? I of course expect yes, I'm asking because: Your build.xml contains zero performanceCount/warningCount but cppcheck_details.xml contains them. The files are created from the same data source in publisher so they should correspond each other. Plugin version 1.18 should be able to handle all severities (I check it with cppcheck 1.61 and 1.63 several months ago), so noCategoryCount (~other/unknown category) should be always zero at least for these versions. But it is 149 in your case. The value probably contain warning, performance etc. ones, but I have no idea why Can you find any significant difference between your job directory and the one in JENKINS-17450.tar.gz? Please Create a new job with cppcheck analysis of https://github.com/mixalturek/graphal. Perform several builds. Remove code of https://github.com/mixalturek/graphal from workwpace to have a smaller archive. Zip whole job directory as I did for JENKINS-17450.tar.gz and attach it. Thank you! 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.
[JIRA] [cppcheck] (JENKINS-17450) warning and performance not counted
Michal Turek updated JENKINS-17450 warning and performance not counted Change By: Michal Turek (09/Jul/14 7:51 PM) Attachment: JENKINS-17450.tar.gz 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.
[JIRA] [cppcheck] (JENKINS-17450) warning and performance not counted
Michal Turek commented on JENKINS-17450 warning and performance not counted Hi James, please attach or send me config.xml (job directory), build.xml (build directory), cppcheck_details.xml (build directory), source cppcheck report (workspace directory) and maybe screenshot of configuration page. If there are any sensitive data, please delete them or send me at least cppcheck related parts of the files. What version of Jenkins core and cppcheck do you use and on which platform? Thank you, Michal 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.
[JIRA] [cppcheck] (JENKINS-23185) Setting build status to FAILURE for new error when errors were fixed
Michal Turek commented on JENKINS-23185 Setting build status to FAILURE for new error when errors were fixed I will try to simulate the issue and debug the code... 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.
[JIRA] [cppcheck] (JENKINS-23185) Setting build status to FAILURE for new error when errors were fixed
Michal Turek assigned JENKINS-23185 to Michal Turek Setting build status to FAILURE for new error when errors were fixed Change By: Michal Turek (05/Jul/14 7:36 PM) Assignee: GregoryBoissinot MichalTurek 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.
[JIRA] [cppcheck] (JENKINS-23247) Display trends graph last 10/20 sucessful/fail builds in CPPcheck plugin.
Michal Turek commented on JENKINS-23247 Display trends graph last 10/20 sucessful/fail builds in CPPcheck plugin. Hi Senthil, I'm sorry, I don't understand your description, can you rewrite it in different words, please? Concrete questions: What happened during builds 50 and 337? Were they successful or failed? I guess all of them failed, correct? Does build.xml results contain Cppcheck data for the builds between 50 and 337? If no, is something important in the build logs for that builds? What does "last successful and current failed" mean? What does "20/30" mean? What do you expect on the screenshot? What version of plugin do you use? Which platform, etc. 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.
[JIRA] [cppcheck] (JENKINS-23185) Setting build status to FAILURE for new error when errors were fixed
Michal Turek commented on JENKINS-23185 Setting build status to FAILURE for new error when errors were fixed Hi Jan, I think, the description of the configuration fields is little misleading, which probably confused you. It uses word "errors" in meaning of "whatever type of issue". Cppcheck tool reports "errors" (of several types/severities) instead of "issues" or "violations", please check its manual. So, if I understand your description correctly... "1" is configured for "New" threshold to fail the build (red circle). Build N had 6 errors in total. Build N+1 had 4 errors and 26 warnings in total. 26 + 4 = 30 and 30 - 6 1, so the build was marked as failed, which is fully correct. I have never used this part of the plugin and I don't know the relevant code much. Did I miss something? If everything I wrote above is correct, do you think I should update the labels and tool tips in the configuration page? The current state is fully OK for me, I'm quite familiar with Cppcheck and the plugin. But new users can have troubles with that. What do you think? Thanks, Michal 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.
[JIRA] [cppcheck] (JENKINS-22965) Cppcheck plugin shall display the inconclusive messages
Michal Turek commented on JENKINS-22965 Cppcheck plugin shall display the inconclusive messages Maven told me the release was successful and a new tag is present in git, but something went wrong. I'm probably facing to this issue https://groups.google.com/d/topic/jenkinsci-dev/qkmbl3HrYgk/discussion, but who knows. I have just tried to re-release the plugin once more using the commands below which should workaround the issue. We will see tomorrow. mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare mvn org.apache.maven.plugins:maven-release-plugin:2.5:perform Thanks for notification, I appreciate that. 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.
[JIRA] [cppcheck] (JENKINS-22965) Cppcheck plugin shall display the inconclusive messages
Michal Turek started work on JENKINS-22965 Cppcheck plugin shall display the inconclusive messages Change By: Michal Turek (18/May/14 7:22 AM) Status: Open InProgress 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.
[JIRA] [cppcheck] (JENKINS-22965) Cppcheck plugin shall display the inconclusive messages
Michal Turek assigned JENKINS-22965 to Michal Turek Cppcheck plugin shall display the inconclusive messages Change By: Michal Turek (18/May/14 7:22 AM) Assignee: GregoryBoissinot MichalTurek 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.
[JIRA] [cppcheck] (JENKINS-22965) Cppcheck plugin shall display the inconclusive messages
Michal Turek updated JENKINS-22965 Cppcheck plugin shall display the inconclusive messages Change By: Michal Turek (18/May/14 9:07 AM) Attachment: details.png 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.
[JIRA] [cppcheck] (JENKINS-22965) Cppcheck plugin shall display the inconclusive messages
Michal Turek updated JENKINS-22965 Cppcheck plugin shall display the inconclusive messages Change By: Michal Turek (18/May/14 9:07 AM) Attachment: all_violations.png 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.
[JIRA] [cppcheck] (JENKINS-22965) Cppcheck plugin shall display the inconclusive messages
Michal Turek resolved JENKINS-22965 as Fixed Cppcheck plugin shall display the inconclusive messages Implemented, will be released in version 1.17. Change By: Michal Turek (18/May/14 9:12 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 -- 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.
[JIRA] [cppcheck] (JENKINS-22965) Cppcheck plugin shall display the inconclusive messages
Michal Turek closed JENKINS-22965 as Fixed Cppcheck plugin shall display the inconclusive messages Change By: Michal Turek (18/May/14 9:15 AM) Status: Resolved Closed 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.
[JIRA] [cppcheck] (JENKINS-23086) Cppcheck plugin shall display verbose information
Michal Turek created JENKINS-23086 Cppcheck plugin shall display verbose information Issue Type: Improvement Affects Versions: current Assignee: Michal Turek Components: cppcheck Created: 18/May/14 11:21 AM Description: The plugin doesn't work with verbose information present in report file produced by cppcheck. It should be stored and displayed to the user. error id="arrayIndexThenCheck" severity="style" msg="Array index 'index' is used before limits check." verbose="Defensive programming: The variable 'index' is used as an array index before it is check that is within limits. This can mean that the array might be accessed out of bounds. Reorder conditions such as '(a[i] amp;amp; i lt; 10)' to '(i lt; 10 amp;amp; a[i])'. That way the array will not be accessed if the index is out of limits." /error Environment: 1.16 Project: Jenkins Priority: Major Reporter: Michal Turek 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.
[JIRA] [cppcheck] (JENKINS-23086) Cppcheck plugin shall display verbose information
Michal Turek started work on JENKINS-23086 Cppcheck plugin shall display verbose information Change By: Michal Turek (18/May/14 11:26 AM) Status: Open InProgress 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.
[JIRA] [cppcheck] (JENKINS-23086) Cppcheck plugin shall display verbose information
Michal Turek updated JENKINS-23086 Cppcheck plugin shall display verbose information Change By: Michal Turek (18/May/14 11:44 AM) Attachment: all_violations.png Attachment: source_tooltip.png 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.
[JIRA] [cppcheck] (JENKINS-23086) Cppcheck plugin shall display verbose information
Michal Turek closed JENKINS-23086 as Fixed Cppcheck plugin shall display verbose information Change By: Michal Turek (18/May/14 11:49 AM) Status: Resolved Closed 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.
[JIRA] [cppcheck] (JENKINS-23086) Cppcheck plugin shall display verbose information
Michal Turek resolved JENKINS-23086 as Fixed Cppcheck plugin shall display verbose information Implemented, will be released in version 1.17. Change By: Michal Turek (18/May/14 11:48 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 -- 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.
[JIRA] [cppcheck] (JENKINS-23086) Cppcheck plugin shall display verbose information
Michal Turek
updated JENKINS-23086
Cppcheck plugin shall display verbose information
Change By:
Michal Turek
(18/May/14 11:25 AM)
Description:
Theplugindoesntworkwith
{{
verbose
}}
informationpresentin
the
reportfileproducedbycppcheck
,itusesonly{{msg}}attribute
.Itshouldbestoredanddisplayedtotheuser
too
.{noformat}error
id=arrayIndexThenCheck
severity=style
msg=Arrayindexindexisusedbeforelimitscheck.
verbose=Defensiveprogramming:Thevariableindexisused
asanarrayindexbeforeitischeckthatiswithinlimits.
Thiscanmeanthatthearraymightbeaccessedoutofbounds.
Reorderconditionssuchas(a[i]amp;amp;ilt;10)to
(ilt;10amp;amp;a[i]).Thatwaythearraywillnot
beaccessediftheindexisoutoflimits./error{noformat}
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.
[JIRA] [cppcheck] (JENKINS-22761) Missing links to source in cppcheck plugin
Michal Turek started work on JENKINS-22761 Missing links to source in cppcheck plugin Change By: Michal Turek (27/Apr/14 2:37 PM) Status: Open InProgress 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.
[JIRA] [cppcheck] (JENKINS-22761) Missing links to source in cppcheck plugin
Michal Turek commented on JENKINS-22761 Missing links to source in cppcheck plugin Ok, I understand now. You probably execute Cppcheck from a sub-directory of the workspace, but the plugin expects all paths in the report are relative to the workspace. I have just added "Report in a sub-directory of the workspace (advanced)" section to the plugin wiki, there are two possible solutions to your problem. Please let me know if such help is sufficient for you, I will reject the task in such case. 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.
[JIRA] [cppcheck] (JENKINS-22761) Missing links to source in cppcheck plugin
Michal Turek assigned JENKINS-22761 to Michal Turek Missing links to source in cppcheck plugin Change By: Michal Turek (25/Apr/14 4:04 PM) Assignee: GregoryBoissinot MichalTurek 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.
[JIRA] [cppcheck] (JENKINS-22761) Missing links to source in cppcheck plugin
Michal Turek commented on JENKINS-22761 Missing links to source in cppcheck plugin Hi, can you attach a screenshot? The issues that were in the previous build but are solved in the current build (the green ones) doesn't contain the link, it is a "feature". It would require a change of data model and was just too difficult to implement. 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.
[JIRA] [disk-usage] (JENKINS-22721) Project page has broken layout on smaller screens
Michal Turek started work on JENKINS-22721 Project page has broken layout on smaller screens Change By: Michal Turek (22/Apr/14 6:46 PM) Status: Open InProgress 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.
[JIRA] [disk-usage] (JENKINS-22721) Project page has broken layout on smaller screens
Michal Turek created JENKINS-22721 Project page has broken layout on smaller screens Issue Type: Bug Affects Versions: current Assignee: Michal Turek Attachments: projectaction_layout_after.png, projectaction_layout_before.png Components: disk-usage Created: 22/Apr/14 6:46 PM Description: Floating box with the graph on the project page contains a long line which increases the box width and breaks the layout. The text can be moved to a new "disk usage" section with large icon and the same information. See the attached screenshots. Environment: Version 0.23 Project: Jenkins Priority: Major Reporter: Michal Turek 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.
[JIRA] [disk-usage] (JENKINS-22721) Project page has broken layout on smaller screens
Michal Turek commented on JENKINS-22721 Project page has broken layout on smaller screens Fixed in https://github.com/mixalturek/disk-usage-plugin/commit/f00e12df71070b87a09535488ed6b0800d9125d2, pull request sent. 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.
[JIRA] [disk-usage] (JENKINS-16856) Plugin uses hostname for links instead of ip address
Michal Turek commented on JENKINS-16856 Plugin uses hostname for links instead of ip address It seems the issue has been already fixed in https://github.com/jenkinsci/disk-usage-plugin/commit/454be7a46fd59418acfa9e5ab7386cab436ba42d about half a year ago. The fix is present in latest released version 0.23 too. DiskUsageManagement.getUrlName() returns "disk-usage" string, which is then used as a relative path to the parent object/page. Verified in debugger that this method produces the address. The link is correct while accessing both from http://localhost:9000/ and http://127.0.0.1:9000/. The issue can be closed as 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 -- 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.
[JIRA] [disk-usage] (JENKINS-16856) Plugin uses hostname for links instead of ip address
Michal Turek started work on JENKINS-16856 Plugin uses hostname for links instead of ip address Change By: Michal Turek (19/Apr/14 1:22 PM) Status: Open InProgress 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.
[JIRA] [disk-usage] (JENKINS-16856) Plugin uses hostname for links instead of ip address
Michal Turek closed JENKINS-16856 as Fixed Plugin uses hostname for links instead of ip address Change By: Michal Turek (19/Apr/14 1:22 PM) Status: Resolved Closed 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.
