[JIRA] (JENKINS-12186) warnings per project dashboard portlet should allow un-used columns to be turned off, same as warnings trend (type distribution does)

[ https://issues.jenkins-ci.org/browse/JENKINS-12186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner resolved JENKINS-12186. --- Resolution: Fixed warnings per project dashboard portlet should allow un-used columns

[JIRA] (JENKINS-12662) Contolling (disabling/enabling) a build step by a flag

[ https://issues.jenkins-ci.org/browse/JENKINS-12662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner resolved JENKINS-12662. --- Resolution: Fixed There is a plugin for that: flexible build step.

[JIRA] (JENKINS-12482) Warnings not detected when file path does not appear after [WARNING]

[ https://issues.jenkins-ci.org/browse/JENKINS-12482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158744#comment-158744 ] Ulli Hafner commented on JENKINS-12482: --- Ok, I see. Seems that I need to add an

[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings

[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158745#comment-158745 ] Ulli Hafner edited comment on JENKINS-12424 at 2/7/12 9:19 PM: ---

[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings

[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158745#comment-158745 ] Ulli Hafner edited comment on JENKINS-12424 at 2/7/12 9:21 PM: ---

[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings

[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158745#comment-158745 ] Ulli Hafner commented on JENKINS-12424: --- Ok, I added the message to the build summary:

[JIRA] (JENKINS-12692) Plugin destroys configuration of Publishers

[ https://issues.jenkins-ci.org/browse/JENKINS-12692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner updated JENKINS-12692: -- Description: After installing the flexible-publish plugin, the Publishers of some jobs get

[JIRA] (JENKINS-12692) Plugin destroys configuration of Publishers

[ https://issues.jenkins-ci.org/browse/JENKINS-12692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner updated JENKINS-12692: -- Description: After installing the flexible-publish plugin, the Publishers of some jobs get

[JIRA] (JENKINS-12692) Plugin destroys configuration of Publishers

[ https://issues.jenkins-ci.org/browse/JENKINS-12692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158852#comment-158852 ] Ulli Hafner commented on JENKINS-12692: --- After removing the flexible-publisher and

[JIRA] (JENKINS-12182) Publisher - Code Analysis - NullPointerException

[ https://issues.jenkins-ci.org/browse/JENKINS-12182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158853#comment-158853 ] Ulli Hafner commented on JENKINS-12182: --- Can you please check if removing

[JIRA] (JENKINS-12482) Warnings not detected when file path does not appear after [WARNING]

[ https://issues.jenkins-ci.org/browse/JENKINS-12482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-12482 started by Ulli Hafner. Warnings not detected when file path does not appear after [WARNING]

[JIRA] (JENKINS-12612) CVS plugin creates hundreds of 'cvs server' processes which kill our Jenkins server

[ https://issues.jenkins-ci.org/browse/JENKINS-12612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158949#comment-158949 ] Ulli Hafner commented on JENKINS-12612: --- Sorry about the late answer, seems that my

[JIRA] (JENKINS-12743) Warnings plugin does not aggregate for multi-configuration projects

[ https://issues.jenkins-ci.org/browse/JENKINS-12743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner resolved JENKINS-12743. --- Resolution: Duplicate Warnings plugin does not aggregate for multi-configuration

[JIRA] (JENKINS-12692) Plugin destroys configuration of Publishers

[ https://issues.jenkins-ci.org/browse/JENKINS-12692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158993#comment-158993 ] Ulli Hafner commented on JENKINS-12692: --- I see, that would solve the problem for my

[JIRA] (JENKINS-11846) Plugin is not showing the path for the package grouping for all warnings that are not from Java or C# files

[ https://issues.jenkins-ci.org/browse/JENKINS-11846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159006#comment-159006 ] Ulli Hafner commented on JENKINS-11846: --- Integrated in

[JIRA] (JENKINS-11926) Warnings plugin does not work on a slave

[ https://issues.jenkins-ci.org/browse/JENKINS-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159022#comment-159022 ] Ulli Hafner commented on JENKINS-11926: --- @Hendrik Fuß: please file a new bug report if

[JIRA] (JENKINS-11926) Warnings plugin does not work on a slave

[ https://issues.jenkins-ci.org/browse/JENKINS-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159024#comment-159024 ] Ulli Hafner commented on JENKINS-11926: --- @Christian: is this issue still present with

[JIRA] (JENKINS-8185) Exception in WarningsPlugin

[ https://issues.jenkins-ci.org/browse/JENKINS-8185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner resolved JENKINS-8185. -- Resolution: Fixed Fixed in flexible-publisher plug-in, see JENKINS-12692.

[JIRA] (JENKINS-12793) Why the Post Steps and Post-build Actions are not executed after the build finished

[ https://issues.jenkins-ci.org/browse/JENKINS-12793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner updated JENKINS-12793: -- Assignee: (was: Ulli Hafner) Component/s: postbuild-task

[JIRA] (JENKINS-11926) Warnings plugin does not work on a slave

[ https://issues.jenkins-ci.org/browse/JENKINS-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner updated JENKINS-11926: -- Attachment: issue11926.txt Massimo, I think that the problem must be somewhere else. Maybe

[JIRA] (JENKINS-12822) Java import of deprecated type not recognized as warning

[ https://issues.jenkins-ci.org/browse/JENKINS-12822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner updated JENKINS-12822: -- Priority: Minor (was: Major) Java import of deprecated type not recognized as warning

[JIRA] (JENKINS-12822) Java import of deprecated type not recognized as warning

[ https://issues.jenkins-ci.org/browse/JENKINS-12822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159310#comment-159310 ] Ulli Hafner commented on JENKINS-12822: --- Integrated in

[JIRA] (JENKINS-12860) klocwork should use analysis core so it can be rolled up with its own type by static analysis portlets

[ https://issues.jenkins-ci.org/browse/JENKINS-12860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner reassigned JENKINS-12860: - Assignee: gbois (was: Ulli Hafner) How is the current implememtation working? Is this

[JIRA] (JENKINS-12309) java.lang.reflect.InvocationTargetException - warnings trend by type distribution portlet

[ https://issues.jenkins-ci.org/browse/JENKINS-12309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner resolved JENKINS-12309. --- Resolution: Fixed java.lang.reflect.InvocationTargetException - warnings trend by

[JIRA] (JENKINS-12223) Warnings trend graph (type distribution) dashboard portlet is very slow to display when # jobs in view 12 or so

[ https://issues.jenkins-ci.org/browse/JENKINS-12223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner resolved JENKINS-12223. --- Resolution: Fixed Warnings trend graph (type distribution) dashboard portlet is very

[JIRA] (JENKINS-12186) warnings per project dashboard portlet should allow un-used columns to be turned off, same as warnings trend (type distribution does)

[ https://issues.jenkins-ci.org/browse/JENKINS-12186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner reopened JENKINS-12186: --- This is a new bug. warnings per project dashboard portlet should allow

[JIRA] (JENKINS-12602) Detection of first build seems to be broken

[ https://issues.jenkins-ci.org/browse/JENKINS-12602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-12602 started by Ulli Hafner. Detection of first build seems to be broken --- Key:

[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings

[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner reopened JENKINS-12424: --- Yes, that would improve that usability even more. Since this feature needs the HTML links

[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs

[ https://issues.jenkins-ci.org/browse/JENKINS-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner updated JENKINS-12972: -- Component/s: git Add option to run 'git bisect' to find which commit added new bugs

[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs

[ https://issues.jenkins-ci.org/browse/JENKINS-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner updated JENKINS-12972: -- Component/s: analysis-core core Add option to run 'git bisect' to find

[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs

[ https://issues.jenkins-ci.org/browse/JENKINS-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159832#comment-159832 ] Ulli Hafner edited comment on JENKINS-12972 at 3/5/12 10:00 AM:

[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs

[ https://issues.jenkins-ci.org/browse/JENKINS-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159836#comment-159836 ] Ulli Hafner commented on JENKINS-12972: --- I think the best approach would be to have a

[JIRA] (JENKINS-12984) warnings (et.al) per project - add checkbox to filter out projects with issue total of 0? - or to show only the top N based on sort selection?

[ https://issues.jenkins-ci.org/browse/JENKINS-12984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159864#comment-159864 ] Ulli Hafner commented on JENKINS-12984: --- Can you please provide a fake screenshot or

[JIRA] (JENKINS-12307) Stack Trace when going to main configuration page

[ https://issues.jenkins-ci.org/browse/JENKINS-12307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159870#comment-159870 ] Ulli Hafner commented on JENKINS-12307: --- @Curtis: This issue is only about an

[JIRA] (JENKINS-5905) Static Analysis graphs should appear after the test results

[ https://issues.jenkins-ci.org/browse/JENKINS-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159903#comment-159903 ] Ulli Hafner commented on JENKINS-5905: -- I think this bug is now fixed when the

[JIRA] (JENKINS-13002) FileNotFoundException when trying to install version 1.22 of analysis collector plugin

[ https://issues.jenkins-ci.org/browse/JENKINS-13002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner updated JENKINS-13002: -- Assignee: (was: Ulli Hafner) Component/s: (was: analysis-collector)

[JIRA] (JENKINS-13009) Updates create a lot of Jira user sessions

Ulli Hafner created JENKINS-13009: - Summary: Updates create a lot of Jira user sessions Key: JENKINS-13009 URL: https://issues.jenkins-ci.org/browse/JENKINS-13009 Project: Jenkins Issue

[JIRA] (JENKINS-13030) Canceling subversion checkout fails a build

Ulli Hafner created JENKINS-13030: - Summary: Canceling subversion checkout fails a build Key: JENKINS-13030 URL: https://issues.jenkins-ci.org/browse/JENKINS-13030 Project: Jenkins Issue

[JIRA] (JENKINS-13020) DRY kills job publisher when out of memory - java.lang.OutOfMemoryError: Java heap space

[ https://issues.jenkins-ci.org/browse/JENKINS-13020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160055#comment-160055 ] Ulli Hafner commented on JENKINS-13020: --- How big is that file? DRY

[JIRA] (JENKINS-6971) doxygen 1.7.1 warnings are not logged

[ https://issues.jenkins-ci.org/browse/JENKINS-6971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner resolved JENKINS-6971. -- Resolution: Fixed Ok, then I'm closing this issue. doxygen 1.7.1 warnings

[JIRA] (JENKINS-6748) Analysis of Checkstyle Warnings per User

[ https://issues.jenkins-ci.org/browse/JENKINS-6748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160174#comment-160174 ] Ulli Hafner commented on JENKINS-6748: -- If I remember correctly two volunteers wanted to

[JIRA] (JENKINS-13068) Failed tests are not shown on main page in maven jobs

Ulli Hafner created JENKINS-13068: - Summary: Failed tests are not shown on main page in maven jobs Key: JENKINS-13068 URL: https://issues.jenkins-ci.org/browse/JENKINS-13068 Project: Jenkins

[JIRA] (JENKINS-13056) Obtain reference build from SCM/Trigger

[ https://issues.jenkins-ci.org/browse/JENKINS-13056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner updated JENKINS-13056: -- Summary: Obtain reference build from SCM/Trigger (was: Warnigs Reference Build from

[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs

[ https://issues.jenkins-ci.org/browse/JENKINS-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner updated JENKINS-12972: -- Assignee: (was: Ulli Hafner) Unassigning since this needs some work in core first.

[JIRA] (JENKINS-10319) Ability to change the name Compiler as seen in a lot of the displays

[ https://issues.jenkins-ci.org/browse/JENKINS-10319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160229#comment-160229 ] Ulli Hafner commented on JENKINS-10319: --- Update: I now finished the prototype which

[JIRA] (JENKINS-13056) Obtain reference build from SCM/Trigger

[ https://issues.jenkins-ci.org/browse/JENKINS-13056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160278#comment-160278 ] Ulli Hafner commented on JENKINS-13056: --- Ok, I understand. I.e. we need some kind of

[JIRA] (JENKINS-13090) NoSuchMethodError with the findbugs plugin

[ https://issues.jenkins-ci.org/browse/JENKINS-13090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner resolved JENKINS-13090. --- Resolution: Fixed Fixed in 4.36 NoSuchMethodError with the findbugs

[JIRA] (JENKINS-13101) Analysis Collector Plugin prevents other plugins from loading when the Dashboard View Plugin is not installed

[ https://issues.jenkins-ci.org/browse/JENKINS-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160342#comment-160342 ] Ulli Hafner commented on JENKINS-13101: --- I don't see any references to the analysis

[JIRA] (JENKINS-10319) Ability to change the name Compiler as seen in a lot of the displays

[ https://issues.jenkins-ci.org/browse/JENKINS-10319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160647#comment-160647 ] Ulli Hafner commented on JENKINS-10319: --- Integrated in

[JIRA] (JENKINS-10319) Ability to change the name Compiler as seen in a lot of the displays

[ https://issues.jenkins-ci.org/browse/JENKINS-10319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160827#comment-160827 ] Ulli Hafner commented on JENKINS-10319: --- Nigel, do you think the configuration of the

[JIRA] (JENKINS-10319) Ability to change the name Compiler as seen in a lot of the displays

[ https://issues.jenkins-ci.org/browse/JENKINS-10319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160924#comment-160924 ] Ulli Hafner commented on JENKINS-10319: --- Integrated in

[JIRA] (JENKINS-13278) Avator images should be shown on people page

Ulli Hafner created JENKINS-13278: - Summary: Avator images should be shown on people page Key: JENKINS-13278 URL: https://issues.jenkins-ci.org/browse/JENKINS-13278 Project: Jenkins Issue

[JIRA] (JENKINS-13278) Avator images should be shown on people page

[ https://issues.jenkins-ci.org/browse/JENKINS-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner updated JENKINS-13278: -- Assignee: oxcafebabe Avator images should be shown on people page

[JIRA] (JENKINS-13002) FileNotFoundException when trying to install version 1.22 of analysis collector plugin

[ https://issues.jenkins-ci.org/browse/JENKINS-13002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner resolved JENKINS-13002. --- Resolution: Fixed I just made a new release 1.24. Hopefully this will be synched to the

[JIRA] (JENKINS-13340) Compiler Warnings menu item gone when no compiler warnings

[ https://issues.jenkins-ci.org/browse/JENKINS-13340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner resolved JENKINS-13340. --- Resolution: Not A Defect That is the intended behavior. The link to the details page is

[JIRA] (JENKINS-13340) Compiler Warnings menu item gone when no compiler warnings

[ https://issues.jenkins-ci.org/browse/JENKINS-13340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161216#comment-161216 ] Ulli Hafner commented on JENKINS-13340: --- Actually, we are talking about two links. The

[JIRA] (JENKINS-13124) Missing New warnings

[ https://issues.jenkins-ci.org/browse/JENKINS-13124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner updated JENKINS-13124: -- Priority: Minor (was: Major) Seems that your links are expired. Do you mind providing the

[JIRA] (JENKINS-13101) Analysis Collector Plugin prevents other plugins from loading when the Dashboard View Plugin is not installed

[ https://issues.jenkins-ci.org/browse/JENKINS-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161224#comment-161224 ] Ulli Hafner commented on JENKINS-13101: --- Ok, I can reproduce the problem with 1.458.

[JIRA] (JENKINS-12124) random NoClassDefFoundError: hudson/plugins/analysis/core/AbstractProjectAction - Not all jobs loaded

[ https://issues.jenkins-ci.org/browse/JENKINS-12124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161274#comment-161274 ] Ulli Hafner commented on JENKINS-12124: --- I still can't reproduce this problem. I'm not

[JIRA] (JENKINS-10319) Ability to change the name Compiler as seen in a lot of the displays

[ https://issues.jenkins-ci.org/browse/JENKINS-10319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161313#comment-161313 ] Ulli Hafner commented on JENKINS-10319: --- Integrated in

[JIRA] (JENKINS-10319) Ability to change the name Compiler as seen in a lot of the displays

[ https://issues.jenkins-ci.org/browse/JENKINS-10319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161484#comment-161484 ] Ulli Hafner commented on JENKINS-10319: --- Integrated in

[JIRA] (JENKINS-13414) Issue while building jenkinsci-pmd-plugin-a16ba49 source code

[ https://issues.jenkins-ci.org/browse/JENKINS-13414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner resolved JENKINS-13414. --- Resolution: Cannot Reproduce Does it compile without your changes? What did you change in

[JIRA] (JENKINS-13379) jenkins ver. 1.458 crash with analysis-collector 1.24

[ https://issues.jenkins-ci.org/browse/JENKINS-13379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner updated JENKINS-13379: -- Assignee: vjuranek (was: Ulli Hafner) Description: jenkins ver. 1.458 crash with

[JIRA] (JENKINS-10319) Ability to change the name Compiler as seen in a lot of the displays

[ https://issues.jenkins-ci.org/browse/JENKINS-10319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161542#comment-161542 ] Ulli Hafner commented on JENKINS-10319: --- If you are interested in testing the

[JIRA] (JENKINS-13532) Changing analysis-core's tab makes breadcrumbs bar move down

[ https://issues.jenkins-ci.org/browse/JENKINS-13532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161805#comment-161805 ] Ulli Hafner commented on JENKINS-13532: --- If I don't call Behaviour.apply then the

[JIRA] (JENKINS-13573) Warnings plugin not supporting the eclipse compiler any more

[ https://issues.jenkins-ci.org/browse/JENKINS-13573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161937#comment-161937 ] Ulli Hafner commented on JENKINS-13573: --- Sorry, then name of the parser has been

[JIRA] (JENKINS-13573) Warnings plugin not supporting the eclipse compiler any more

[ https://issues.jenkins-ci.org/browse/JENKINS-13573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161963#comment-161963 ] Ulli Hafner commented on JENKINS-13573: --- Will be in release 4.4.

[JIRA] (JENKINS-13578) sortbottom does not work anymore in tables

Ulli Hafner created JENKINS-13578: - Summary: sortbottom does not work anymore in tables Key: JENKINS-13578 URL: https://issues.jenkins-ci.org/browse/JENKINS-13578 Project: Jenkins Issue

[JIRA] (JENKINS-13578) sortbottom does not work anymore in tables

[ https://issues.jenkins-ci.org/browse/JENKINS-13578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161978#comment-161978 ] Ulli Hafner commented on JENKINS-13578: --- I hope you don't mind that I assigned you

[JIRA] (JENKINS-13532) Changing analysis-core's tab makes breadcrumbs bar move down

[ https://issues.jenkins-ci.org/browse/JENKINS-13532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161984#comment-161984 ] Ulli Hafner commented on JENKINS-13532: --- Integrated in

[JIRA] (JENKINS-12984) warnings (et.al) per project - add checkbox to filter out projects with issue total of 0? - or to show only the top N based on sort selection?

[ https://issues.jenkins-ci.org/browse/JENKINS-12984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161983#comment-161983 ] Ulli Hafner commented on JENKINS-12984: --- Integrated in

[JIRA] (JENKINS-13491) Marked line in source code lister of Warnings plugin is not visible

[ https://issues.jenkins-ci.org/browse/JENKINS-13491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162146#comment-162146 ] Ulli Hafner commented on JENKINS-13491: --- Integrated in

[JIRA] (JENKINS-13656) Trend graph is shifted

[ https://issues.jenkins-ci.org/browse/JENKINS-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162307#comment-162307 ] Ulli Hafner commented on JENKINS-13656: --- Can you please provide more details. Eg.

[JIRA] (JENKINS-13656) Trend graph is shifted

[ https://issues.jenkins-ci.org/browse/JENKINS-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162316#comment-162316 ] Ulli Hafner commented on JENKINS-13656: --- Hmm, seems that there is no result at all (0

[JIRA] (JENKINS-13656) Trend graph is shifted

[ https://issues.jenkins-ci.org/browse/JENKINS-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162317#comment-162317 ] Ulli Hafner commented on JENKINS-13656: --- And please attach the build.xml file of your

[JIRA] (JENKINS-13656) Trend graph shows zero instead of actual value

[ https://issues.jenkins-ci.org/browse/JENKINS-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner updated JENKINS-13656: -- Description: The trend graph does not show all results. At least for one build zero is shown

[JIRA] (JENKINS-13656) Trend graph shows zero instead of actual value

[ https://issues.jenkins-ci.org/browse/JENKINS-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner updated JENKINS-13656: -- Summary: Trend graph shows zero instead of actual value (was: Trend graph is shifted)

[JIRA] (JENKINS-13656) Trend graph shows zero instead of actual value

[ https://issues.jenkins-ci.org/browse/JENKINS-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162318#comment-162318 ] Ulli Hafner commented on JENKINS-13656: --- And finally: can you start another build just

[JIRA] (JENKINS-13656) Trend graph shows zero instead of actual value

[ https://issues.jenkins-ci.org/browse/JENKINS-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162318#comment-162318 ] Ulli Hafner edited comment on JENKINS-13656 at 5/2/12 12:03 PM:

[JIRA] (JENKINS-13656) Trend graph shows zero instead of actual value

[ https://issues.jenkins-ci.org/browse/JENKINS-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162322#comment-162322 ] Ulli Hafner commented on JENKINS-13656: --- Sorry, I mean the build.xml file in Jenkins

[JIRA] (JENKINS-13656) Trend graph shows zero instead of actual value

[ https://issues.jenkins-ci.org/browse/JENKINS-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162324#comment-162324 ] Ulli Hafner commented on JENKINS-13656: --- Ok, thanks. From the build.xml I see that

[JIRA] (JENKINS-13656) Trend graph shows values of wrong parser

[ https://issues.jenkins-ci.org/browse/JENKINS-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162397#comment-162397 ] Ulli Hafner commented on JENKINS-13656: --- Integrated in

[JIRA] (JENKINS-13656) Trend graph shows values of wrong parser

[ https://issues.jenkins-ci.org/browse/JENKINS-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162500#comment-162500 ] Ulli Hafner commented on JENKINS-13656: --- Integrated in

[JIRA] (JENKINS-13716) Default graph configuration for project is not read

Ulli Hafner created JENKINS-13716: - Summary: Default graph configuration for project is not read Key: JENKINS-13716 URL: https://issues.jenkins-ci.org/browse/JENKINS-13716 Project: Jenkins

[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings

[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162583#comment-162583 ] Ulli Hafner commented on JENKINS-12424: --- Integrated in

[JIRA] (JENKINS-13718) Plugin status of modules is not propagated to parent module

Ulli Hafner created JENKINS-13718: - Summary: Plugin status of modules is not propagated to parent module Key: JENKINS-13718 URL: https://issues.jenkins-ci.org/browse/JENKINS-13718 Project: Jenkins

[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings

[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162740#comment-162740 ] Ulli Hafner commented on JENKINS-12424: --- Integrated in

[JIRA] (JENKINS-12424) More correct and specific build state change reasons from Warnings

[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner resolved JENKINS-12424. --- Resolution: Fixed More correct and specific build state change reasons from Warnings

[JIRA] (JENKINS-13797) Unstable or failure reason is not printed in build summary

Ulli Hafner created JENKINS-13797: - Summary: Unstable or failure reason is not printed in build summary Key: JENKINS-13797 URL: https://issues.jenkins-ci.org/browse/JENKINS-13797 Project: Jenkins

[JIRA] (JENKINS-13532) Changing analysis-core's tab makes breadcrumbs bar move down

[ https://issues.jenkins-ci.org/browse/JENKINS-13532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162998#comment-162998 ] Ulli Hafner commented on JENKINS-13532: --- Seems that Jenkins uses a new YUI version

[JIRA] (JENKINS-13876) GNU Compiler Warnings also catches Java exception

[ https://issues.jenkins-ci.org/browse/JENKINS-13876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163131#comment-163131 ] Ulli Hafner commented on JENKINS-13876: --- I'm not sure if it is possible to decide if a

[JIRA] (JENKINS-13876) GNU Compiler Warnings also catches Java exception

[ https://issues.jenkins-ci.org/browse/JENKINS-13876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163135#comment-163135 ] Ulli Hafner commented on JENKINS-13876: --- Well, that does not work in general. So I

[JIRA] (JENKINS-13892) Static analyis plugins

[ https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163158#comment-163158 ] Ulli Hafner commented on JENKINS-13892: --- Can you please show the results of the

[JIRA] (JENKINS-13892) Analysis collector marks some warnings as fixed even though they are not

[ https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner updated JENKINS-13892: -- Summary: Analysis collector marks some warnings as fixed even though they are not (was:

[JIRA] (JENKINS-13892) Analysis collector marks some warnings as fixed even though they are not

[ https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner updated JENKINS-13892: -- Environment: Jenkins core version: 1.410 Static Code Analysis Plug-ins -- 1.38 FindBugs

[JIRA] (JENKINS-12307) Stack Trace when going to main configuration page

[ https://issues.jenkins-ci.org/browse/JENKINS-12307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-12307 started by Ulli Hafner. Stack Trace when going to main configuration page -

[JIRA] (JENKINS-11225) Add aggregation and subview for multi-configuration projects

[ https://issues.jenkins-ci.org/browse/JENKINS-11225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163209#comment-163209 ] Ulli Hafner commented on JENKINS-11225: --- Well, I don't use multi-configuration

[JIRA] (JENKINS-12307) Stack Trace when going to main configuration page

[ https://issues.jenkins-ci.org/browse/JENKINS-12307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner resolved JENKINS-12307. --- Resolution: Fixed Stack Trace when going to main configuration page

[JIRA] (JENKINS-13876) GNU Compiler Warnings also catches Java exception

[ https://issues.jenkins-ci.org/browse/JENKINS-13876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner resolved JENKINS-13876. --- Resolution: Not A Defect I see no other solution for this problem (besides the

[JIRA] (JENKINS-13892) Analysis collector marks some warnings as fixed even though they are not

[ https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13892 started by Ulli Hafner. Analysis collector marks some warnings as fixed even though they are not

  1   2   3   4   5   6   7   8   9   10   >