[JIRA] [dashboard-view-plugin] (JENKINS-29690) Icons missing in Build Statistics portlet
Title: Message Title Marco Ambu commented on JENKINS-29690 Re: Icons missing in Build Statistics portlet I am OK to release it, but can another person do that? 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] [artifactdeployer-plugin] (JENKINS-28747) Add option to move files rather than copying
Title: Message Title Marco Ambu created an issue Jenkins / JENKINS-28747 Add option to move files rather than copying Issue Type: Improvement Assignee: Gregory Boissinot Components: artifactdeployer-plugin Created: 04/Jun/15 11:39 AM Priority: Minor Reporter: Marco Ambu As one of the main tasks of this plugin is to separate the build information from the build artifacts, it would be good to have an option to actually move files rather than copying as sometimes we do not want to keep the file in the workspace. Add Comment
[JIRA] [core] (JENKINS-13978) Add posibility to copy view
Title: Message Title Marco Ambu commented on JENKINS-13978 Re: Add posibility to copy view Does anyone know the status of this change? 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] [tap-plugin] (JENKINS-28306) Add title to test graph
Title: Message Title Marco Ambu created an issue Jenkins / JENKINS-28306 Add title to test graph Issue Type: Improvement Assignee: Bruno P. Kinoshita Attachments: TapMissingTitle.png Components: tap-plugin Created: 08/May/15 8:32 AM Environment: Jenkins 1.542 Priority: Minor Reporter: Marco Ambu We may have multiple graphs on a job's main page coming from different plugins. Most of them have a title (usually at the top of the picture) but the TAP test results graph doesn't have one. See attached screenshot: as you can see, there may be confusion looking at the graphs, because the title of the second graph CheckTcl seems to refer to the first graph (which is coming from TAP). The best would be to have an option to specify a title for the TAP graph.
[JIRA] [dashboard-view] (JENKINS-17571) The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process
Marco Ambu commented on JENKINS-17571 The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process I can see that this is assigned to component dashboard-view which is a plugin. Are you using the dashboard-view plugin to display your default job page in Jenkins? If not, you need to choose another component to get this bug looked at. 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/groups/opt_out.
[JIRA] [core] (JENKINS-18070) Unable to load http://localhost:8080 with fresh installation
Marco Ambu updated JENKINS-18070 Unable to load http://localhost:8080 with fresh installation If you loaded a fresh war file, probably you don't have the dashboard-view plugin installed... therefore I have changed the component to core, not sure if there is a better one. Change By: Marco Ambu (11/Jul/13 8:49 AM) Component/s: core Component/s: dashboard-view 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/groups/opt_out.
[JIRA] [core] (JENKINS-18068) Cannot access the jenkins menue, no dashboard functionality!!!
Marco Ambu updated JENKINS-18068 Cannot access the jenkins menue, no dashboard functionality!!! It seems that this issue does not have anything to do with the dashboard-view plugin. Changing component to core... not sure if there is a better one. Change By: Marco Ambu (11/Jul/13 8:50 AM) Component/s: core Component/s: dashboard-view 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/groups/opt_out.
[JIRA] [core] (JENKINS-17181) A list of all bugs/issues per project
Marco Ambu updated JENKINS-17181 A list of all bugs/issues per project Removed the dashboard-view plugin component Change By: Marco Ambu (11/Jul/13 8:51 AM) Component/s: core Component/s: dashboard-view 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/groups/opt_out.
[JIRA] [dashboard-view] (JENKINS-17314) Rebuild Job using GET method
Marco Ambu commented on JENKINS-17314 Rebuild Job using GET method 2.6 is out there. 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/groups/opt_out.
[JIRA] (JENKINS-12519) Test Statistic Grid will be rendered diffrently in IE9, Chrome, FF, Opera
Marco Ambu resolved JENKINS-12519 as Fixed Test Statistic Grid will be rendered diffrently in IE9, Chrome, FF, Opera Text alignment in the table should be fixed in latest release. Change By: Marco Ambu (29/Mar/13 3:29 PM) Status: Open 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/groups/opt_out.
[JIRA] (JENKINS-12519) Test Statistic Grid will be rendered diffrently in IE9, Chrome, FF, Opera
Marco Ambu stopped work on JENKINS-12519 Test Statistic Grid will be rendered diffrently in IE9, Chrome, FF, Opera Change By: Marco Ambu (29/Mar/13 3:28 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/groups/opt_out.
[JIRA] (JENKINS-16944) Use div instead of tables for the layout of the dashboard
Marco Ambu started work on JENKINS-16944 Use div instead of tables for the layout of the dashboard Change By: Marco Ambu (28/Feb/13 12:34 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/groups/opt_out.
[JIRA] (JENKINS-16943) Allow sorting rows in the Test Statistic Grid portlet
Marco Ambu started work on JENKINS-16943 Allow sorting rows in the Test Statistic Grid portlet Change By: Marco Ambu (28/Feb/13 12:34 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/groups/opt_out.
[JIRA] (JENKINS-12519) Test Statistic Grid will be rendered diffrently in IE9, Chrome, FF, Opera
Marco Ambu started work on JENKINS-12519 Test Statistic Grid will be rendered diffrently in IE9, Chrome, FF, Opera Change By: Marco Ambu (28/Feb/13 12:35 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/groups/opt_out.
[JIRA] (JENKINS-16943) Allow sorting rows in the Test Statistic Grid portlet
Marco Ambu created JENKINS-16943 Allow sorting rows in the Test Statistic Grid portlet Issue Type: Improvement Assignee: Marco Ambu Components: dashboard-view Created: 25/Feb/13 9:58 AM Description: Allow sorting rows in the test statistic grid portlet according to the columns available. Project: Jenkins Labels: plugin Priority: Major Reporter: Marco Ambu 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/groups/opt_out.
[JIRA] (JENKINS-16944) Use div instead of tables for the layout of the dashboard
Marco Ambu created JENKINS-16944 Use div instead of tables for the layout of the dashboard Issue Type: Improvement Assignee: Marco Ambu Components: dashboard-view Created: 25/Feb/13 10:15 AM Description: Use div instead of tables for the layout of the dashboard portlets. Tables should only be used for displaying data (where applicable). Project: Jenkins Labels: plugin Priority: Major Reporter: Marco Ambu 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/groups/opt_out.
[JIRA] (JENKINS-16300) Dashborad plugin shows 2008R2 / 2012 connected slaves as offline
Marco Ambu commented on JENKINS-16300 Dashborad plugin shows 2008R2 / 2012 connected slaves as offline I have flagged this issue to the person who contributed this portlet. 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/groups/opt_out.
[JIRA] (JENKINS-16408) Initial state of the new dashboard view not user friendly
Marco Ambu assigned JENKINS-16408 to Marco Ambu Initial state of the new dashboard view not user friendly Change By: Marco Ambu (20/Feb/13 9:35 AM) Assignee: PeterHayes MarcoAmbu 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/groups/opt_out.
[JIRA] (JENKINS-16408) Initial state of the new dashboard view not user friendly
Marco Ambu commented on JENKINS-16408 Initial state of the new dashboard view not user friendly Agree 100%. We may start with the standard jenkins job view and maybe two others (the most common? if we know which they are). 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/groups/opt_out.
[JIRA] (JENKINS-16300) Dashborad plugin shows 2008R2 / 2012 connected slaves as offline
Marco Ambu commented on JENKINS-16300 Dashborad plugin shows 2008R2 / 2012 connected slaves as offline Can you please provide more info on how this is related to the dashboard view plugin? Can you please provide a screenshot? 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/groups/opt_out.
[JIRA] (JENKINS-15085) Test Trend portlet zeros results for running build
Marco Ambu assigned JENKINS-15085 to Marco Ambu Test Trend portlet zeros results for running build Change By: Marco Ambu (20/Feb/13 9:40 AM) Assignee: PeterHayes MarcoAmbu 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/groups/opt_out.
[JIRA] (JENKINS-14988) Use different status icons in dashboard for disbaled and canceled jobs
Marco Ambu commented on JENKINS-14988 Use different status icons in dashboard for disbaled and canceled jobs Is there a common way to do so in jenkins? What does jenkins show in the standard job view? 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/groups/opt_out.
[JIRA] (JENKINS-14045) Add ability to change dashboard diagrams time-scale grain for Trend charts
Marco Ambu commented on JENKINS-14045 Add ability to change dashboard diagrams time-scale grain for Trend charts When you select "week" as the time unit for showing the results, how would you suggest us computing the result for that week? Should that be the last test result for that week? 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/groups/opt_out.
[JIRA] (JENKINS-13933) Arrows in dashboard column headings are inconsistent
Marco Ambu updated JENKINS-13933 Arrows in dashboard column headings are inconsistent I think you are talking about the standard job view. Changing component to core as the dashboard view plugin does not control this feature (it is inherited by jenkins' job view). Change By: Marco Ambu (20/Feb/13 9:52 AM) Component/s: core Component/s: dashboard-view 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/groups/opt_out.
[JIRA] (JENKINS-12863) dashboard - jobs list portlet - add summary statistics
Marco Ambu updated JENKINS-12863 dashboard - jobs list portlet - add summary statistics If this information is "per project" I suggest adding it to the project stats plugin. If this information is an average of all projects shown in the view, then you have to suggest which portlet you would like to see it in. Change By: Marco Ambu (20/Feb/13 9:55 AM) Assignee: PeterHayes MarcoAmbu Component/s: project-stats 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/groups/opt_out.
[JIRA] (JENKINS-11989) Build history time line chart doesn't render in Internet Explorer 8.0.6001
Marco Ambu updated JENKINS-11989 Build history time line chart doesnt render in Internet Explorer 8.0.6001 I think this is a core problem, not dashboard view plugin specific. Removed dashboard-view component. Change By: Marco Ambu (20/Feb/13 10:01 AM) Component/s: dashboard-view 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/groups/opt_out.
[JIRA] (JENKINS-10651) Add cppcheck to Dashboard View
Marco Ambu updated JENKINS-10651 Add cppcheck to Dashboard View Hi, we usually go for the other way round. Every plugin can provide a portlet. The dashboard view portlet is a view and does not know anything about the underlying plugin. So it must be implemented in cppcheck plugin (as we do for warnings, coverity, ...). Change By: Marco Ambu (20/Feb/13 10:04 AM) Component/s: cppcheck 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/groups/opt_out.
[JIRA] (JENKINS-15911) needs to build from client workspace
Marco Ambu assigned JENKINS-15911 to Nicolas De Loof needs to build from client workspace Change By: Marco Ambu (24/Nov/12 11:09 PM) Assignee: MarcoAmbu NicolasDeLoof This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15811) The Manage Jenkins page lists Jenkins CLI multiple times
Marco Ambu updated JENKINS-15811 The Manage Jenkins page lists Jenkins CLI multiple times Change By: Marco Ambu (13/Nov/12 11:09 AM) Component/s: core Component/s: dashboard-view This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14212) dashboard-view build fails using JDK 7
Marco Ambu resolved JENKINS-14212 as Fixed dashboard-view build fails using JDK 7 Change By: Marco Ambu (13/Nov/12 11:14 AM) Status: Open Resolved Assignee: PeterHayes MarcoAmbu Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14045) Add ability to change dashboard diagrams time-scale grain for Trend charts
Marco Ambu commented on JENKINS-14045 Add ability to change dashboard diagrams time-scale grain for Trend charts Dirk, can you open another issue as it is different than this one and then we can easily see your suggestion in JIRA. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13968) Dashboard plugin: request for failing jobs portlet
Marco Ambu commented on JENKINS-13968 Dashboard plugin: request for failing jobs portlet Maybe we can make the unstable jobs portlet configurable so that you can specify the 'unstable' condition. Something like: show all unstable show only failed Actually I'm thinking of having only one configurable portlet such as the jobs grid which can be configured to specify what condition the jobs mustsatisfy to be displayed there. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15294) Pop-up menu is not shown when hovering on the job link in dashboard portlets
Marco Ambu resolved JENKINS-15294 as Fixed Pop-up menu is not shown when hovering on the job link in dashboard portlets Change By: Marco Ambu (21/Oct/12 12:41 PM) Status: Open 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
[JIRA] (JENKINS-15294) Pop-up menu is not shown when hovering on the job link in dashboard portlets
Marco Ambu created JENKINS-15294 Pop-up menu is not shown when hovering on the job link in dashboard portlets Issue Type: Bug Affects Versions: current Assignee: Marco Ambu Components: dashboard-view Created: 25/Sep/12 8:05 AM Description: Latest versions of Jenkins show a pop up menu when the mouse pointer is on the job link. When the mouse pointer is on the job link in a portlet, then an empty menu is displayed. We might have to change the way the joblink is created and see if we can reuse the jenkins one directly. Environment: Jenkins 1.467 Project: Jenkins Priority: Major Reporter: Marco Ambu This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9608) NPE when computing build results in NumBuildsStatsBuilder
Marco Ambu commented on JENKINS-9608 NPE when computing build results in NumBuildsStatsBuilder Is this happening with the latest version of both dashboard-view plugin and projectstats plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9766) Triggering a parameterized build from the dashboard does not return to the dashboard
Marco Ambu commented on JENKINS-9766 Triggering a parameterized build from the dashboard does not return to the dashboard Ok, but what happens when you do the same but starting with a view that is not a "dashboard-view"? Which page are you redirect to after hitting "build"? I believe this is not a dashboard-view related issue, but rather a parametrized-build plugin one. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14434) Delete buttons in view configuration not working
Marco Ambu updated JENKINS-14434 Delete buttons in view configuration not working Assigning to component core, removing from dashboard-view. Change By: Marco Ambu (22/Jul/12 8:58 AM) Summary: Deletebuttons fordashboard in view configuration notworking Assignee: PeterHayes Description: Wheneditingaviewthedeletebuttonsontherightsidedontwork.TrieditwithfirefoxandchromiumsoIguessitsnotbrowserrelated. Edit:Thesamehappenstomeafterupgradingto1.474.ItisnotrelatedtothedashboardpluginasIamnotabletodeletecolumnsandfiltersinstandardvieweither. Component/s: core Component/s: dashboard-view This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6988) Exclusive Execution Plugin: Deadlock in Matrix-Projekt running Shell on every node
Marco Ambu resolved JENKINS-6988 as Duplicate Exclusive Execution Plugin: Deadlock in Matrix-Projekt running Shell on every node Same as JENKINS-9919. Closing this one and tracking changes in the new one. Change By: Marco Ambu (20/Jul/12 4:11 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7781) Test Statistics Grid double counting aggregated tests
Marco Ambu commented on JENKINS-7781 Test Statistics Grid double counting aggregated tests I don't understand the behaviour either, but you said that this also happens when displaying the test results in jenkins. This is important because we don't do any special processing with the test results and we get them directly from jenkins APIs. Can you please show me also the standard test result for the main job? Does it show the 5 missing tests? Need to check about the disabled job: do you think we should include it as well in the total count? If not we could "mark it" in a special way so that it does not cause confusion in the table? What version of the dashboard-view plugin are you using? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12126) Test Trend Chart should be able to show only the failures
Marco Ambu resolved JENKINS-12126 as Fixed Test Trend Chart should be able to show only the failures Fixed in version 2.3 Change By: Marco Ambu (17/Jul/12 1:33 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
[JIRA] (JENKINS-7781) Test Statistics Grid double counting aggregated tests
Marco Ambu commented on JENKINS-7781 Test Statistics Grid double counting aggregated tests Is this still an issue? It seems that the dashboard is behaving correctly anyway because you said: In actuality, my main job has 4 tests, and the three sub jobs have 684 tests in total. dashboard-view is reporting that the main job has 684 tests (so it is counting the subs, but not its own), in addition to the sub jobs, for a total of 1368 tests. So if jenkins is not reporting the 4 tests in the main job either, then I don't think we are doing anything wrong in the dashboard portlet. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7781) Test Statistics Grid double counting aggregated tests
Marco Ambu resolved JENKINS-7781 as Not A Defect Test Statistics Grid double counting aggregated tests I'm closing this one. Reopen it, if still an issue. Change By: Marco Ambu (17/Jul/12 1:54 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12246) Create a new button called Queue Now (or do a plugin for this)
[ https://issues.jenkins-ci.org/browse/JENKINS-12246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162338#comment-162338 ] Marco Ambu commented on JENKINS-12246: -- The quiet period has another original meaning in jenkins: it is needed when triggering the build by a change in a repository... anyway I thick this is another feature that has nothing to do with the dashboard view plugin (which uses the standard jenkins links and view to generate most of the UI to be consistent). I believe a new plugin would be the best. Create a new button called Queue Now (or do a plugin for this) -- Key: JENKINS-12246 URL: https://issues.jenkins-ci.org/browse/JENKINS-12246 Project: Jenkins Issue Type: New Feature Components: dashboard-view Reporter: Kat Lim Ruiz Assignee: Peter Hayes Hi it would be a nice feature to have a button called Queue Now that does the Build Now but respecting the quiet period. What I would like to do is that whenever a build started (scheduled, polled or manually) a before build email is sent to QA so they are aware that the application will be down for a few minutes. The quiet period would serve for them to close their work and so on ... (I already have the before build email with email-ext) Today if I do a Build Now, the build starts right away and there is no quiet period. Another way to handle this would be to have a new checkbox that says: Always respect Quiet Period? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12519) Test Statistic Grid will be rendered diffrently in IE9, Chrome, FF, Opera
[ https://issues.jenkins-ci.org/browse/JENKINS-12519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162244#comment-162244 ] Marco Ambu commented on JENKINS-12519: -- Hi, can you please also provide some screenshot? Test Statistic Grid will be rendered diffrently in IE9, Chrome, FF, Opera -- Key: JENKINS-12519 URL: https://issues.jenkins-ci.org/browse/JENKINS-12519 Project: Jenkins Issue Type: Bug Components: dashboard-view Environment: jenkins 1.445 dashboard-view 2.1 IE 9, FF 4-10, chrome, opera Reporter: Thomas Fürer Assignee: Marco Ambu Priority: Minor The job names are displayed in a centric style in IE9 and opera but are displyed left bounded in FF and chrome. I would prefer left bounded. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13257) New Job - Copy existing Job fails with error Status Code: 500
[ https://issues.jenkins-ci.org/browse/JENKINS-13257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Ambu updated JENKINS-13257: - Component/s: (was: dashboard-view) New Job - Copy existing Job fails with error Status Code: 500 Key: JENKINS-13257 URL: https://issues.jenkins-ci.org/browse/JENKINS-13257 Project: Jenkins Issue Type: Bug Components: createjobadvanced Environment: from http://SERVER/systemInfo ALLUSERSPROFILE C:\Dokumente und Einstellungen\All Users BASE c:\Daten\Jenkins\.jenkins COMPUTERNAME WST070736 CSSCRIPT_DIR C:\Programme\ETM\PVSS2\RAG\cs-script ComSpec C:\WINDOWS\system32\cmd.exe CommonProgramFilesC:\Programme\Gemeinsame Dateien DISPLAY wst070736:0.0 DeviceTypeWST EXCURSIONSDK C:\Programme\ETM\PVSS2\3.8 FP_NO_HOST_CHECK NO JENKINS_HOME c:\Daten\Jenkins\.jenkins LC_NO_COMSERVER_REGISTRATION 1 LDMS_LOCAL_DIRC:\Programme\LANDesk\LDClient\Data NIDAQmxSwitchDir C:\Programme\National Instruments\NI-DAQ\Switch\ NUMBER_OF_PROCESSORS 2 OSWindows_NT PATHEXT .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.PSC1 PROCESSOR_ARCHITECTUREx86 PROCESSOR_IDENTIFIER x86 Family 6 Model 15 Stepping 2, GenuineIntel PROCESSOR_LEVEL 6 PROCESSOR_REVISION0f02 PSModulePath C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\ PVSS_II C:\Programme\ETM\PVSS2\3.8\config\config PVSS_II_HOME C:\Programme\ETM\PVSS2\3.8 Path C:\Programme\ETM\PVSS2\3.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\Programme\IVI Foundation\VISA\WinNT\Bin\;C:\Programme\IVI Foundation\VISA\WinNT\Bin;C:\Daten\Python26;C:\Programme\Mozilla Firefox;c:\Programme\Microsoft SQL Server\90\Tools\binn\;C:\Programme\gKP\Bin\;C:\Programme\TortoiseSVN\bin ProgramFiles C:\Programme SystemDrive C: SystemRootC:\WINDOWS TEMP C:\WINDOWS\TEMP TMP C:\WINDOWS\TEMP USERPROFILE C:\Dokumente und Einstellungen\LocalService VISUALSVN_SERVER C:\Programme\VisualSVN Server\ VXIPNPPATHC:\Programme\IVI Foundation\VISA\ gKPDirC:\Programme\gKP\ windirC:\WINDOWS Reporter: Stephan Schwerzmann Labels: jenkins, job, windows New Job - Copy existing Job fails with error Status Code: 500 The job used as source for the copy runs well (our nightly build - hey: it even succeeds :-) The new job is created, but no data is in any of the configuration fields. The new job (empty) can be deleted. Following stacktrace is shown in the Webbrowser: Status Code: 500 Exception: Stacktrace: Warning: Could not find file c:\Daten\Jenkins\.jenkins\jobs\RIMOCTRL_SW_VxWorks-6.7_dev\config.xml to copy. at org.apache.tools.ant.taskdefs.Copy.copySingleFile(Copy.java:573) at org.apache.tools.ant.taskdefs.Copy.execute(Copy.java:403) at hudson.Util.copyFile(Util.java:840) at hudson.model.ItemGroupMixIn.copy(ItemGroupMixIn.java:203) at hudson.model.ItemGroupMixIn.createTopLevelItem(ItemGroupMixIn.java:164) at jenkins.model.Jenkins.doCreateItem(Jenkins.java:2733) at jenkins.model.Jenkins.doCreateItem(Jenkins.java:300) at hudson.model.AllView.doCreateItem(AllView.java:76) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:477) at org.kohsuke.stapler.Stapler.service(Stapler.java:159) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at
[JIRA] (JENKINS-7887) Inconsistency regarding plugin names inside pluginManger pages
[ https://issues.jenkins-ci.org/browse/JENKINS-7887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Ambu reassigned JENKINS-7887: --- Assignee: Marco Ambu Inconsistency regarding plugin names inside pluginManger pages -- Key: JENKINS-7887 URL: https://issues.jenkins-ci.org/browse/JENKINS-7887 Project: Jenkins Issue Type: Bug Components: plugin Reporter: ssbarnea Assignee: Marco Ambu Priority: Minor All the URLs from the /pluginManager/installed should have exact the same names as the plugin - as it is listed inside /pluginManager/available This is really important because I found out that is hard to identify a plugin using the find-in-page search in browser. Just one example (there are tens of them): XShell Plugin is listed as Hudson cross-platform shell plugin, searching by xshell will find nothing. I'm not sure if this could be easily changed but an alternative solution would be just to include the plugin name before the description inside the /installed page. Anyway, the idea is the all the naming must be consistent in order to prevent confusion. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13586) Latest builds portlet show all Jobentries with the current state icon,but it should be the build result state Icon.
[ https://issues.jenkins-ci.org/browse/JENKINS-13586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Ambu reassigned JENKINS-13586: Assignee: Marco Ambu (was: Peter Hayes) Latest builds portlet show all Jobentries with the current state icon,but it should be the build result state Icon. - Key: JENKINS-13586 URL: https://issues.jenkins-ci.org/browse/JENKINS-13586 Project: Jenkins Issue Type: Improvement Components: dashboard-view Affects Versions: current Environment: Jenkins 1.460; Debian Lenny Reporter: Wolfgang Hauser Assignee: Marco Ambu Priority: Minor Fix For: current If a Job changes its state, all entries of this job in Latest builds portlet are prefixed with the same Icon (e.g flashing for currently working). It may be better to take the state of the build number as value for displaying the state of the Job entry. (as it is done in the Build column.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13257) New Job - Copy existing Job fails with error Status Code: 500
[ https://issues.jenkins-ci.org/browse/JENKINS-13257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161891#comment-161891 ] Marco Ambu commented on JENKINS-13257: -- Why is this assigned to dashboard-view plugin? Is that a mistake? New Job - Copy existing Job fails with error Status Code: 500 Key: JENKINS-13257 URL: https://issues.jenkins-ci.org/browse/JENKINS-13257 Project: Jenkins Issue Type: Bug Components: createjobadvanced, dashboard-view Environment: from http://SERVER/systemInfo ALLUSERSPROFILE C:\Dokumente und Einstellungen\All Users BASE c:\Daten\Jenkins\.jenkins COMPUTERNAME WST070736 CSSCRIPT_DIR C:\Programme\ETM\PVSS2\RAG\cs-script ComSpec C:\WINDOWS\system32\cmd.exe CommonProgramFilesC:\Programme\Gemeinsame Dateien DISPLAY wst070736:0.0 DeviceTypeWST EXCURSIONSDK C:\Programme\ETM\PVSS2\3.8 FP_NO_HOST_CHECK NO JENKINS_HOME c:\Daten\Jenkins\.jenkins LC_NO_COMSERVER_REGISTRATION 1 LDMS_LOCAL_DIRC:\Programme\LANDesk\LDClient\Data NIDAQmxSwitchDir C:\Programme\National Instruments\NI-DAQ\Switch\ NUMBER_OF_PROCESSORS 2 OSWindows_NT PATHEXT .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.PSC1 PROCESSOR_ARCHITECTUREx86 PROCESSOR_IDENTIFIER x86 Family 6 Model 15 Stepping 2, GenuineIntel PROCESSOR_LEVEL 6 PROCESSOR_REVISION0f02 PSModulePath C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\ PVSS_II C:\Programme\ETM\PVSS2\3.8\config\config PVSS_II_HOME C:\Programme\ETM\PVSS2\3.8 Path C:\Programme\ETM\PVSS2\3.8\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\Programme\IVI Foundation\VISA\WinNT\Bin\;C:\Programme\IVI Foundation\VISA\WinNT\Bin;C:\Daten\Python26;C:\Programme\Mozilla Firefox;c:\Programme\Microsoft SQL Server\90\Tools\binn\;C:\Programme\gKP\Bin\;C:\Programme\TortoiseSVN\bin ProgramFiles C:\Programme SystemDrive C: SystemRootC:\WINDOWS TEMP C:\WINDOWS\TEMP TMP C:\WINDOWS\TEMP USERPROFILE C:\Dokumente und Einstellungen\LocalService VISUALSVN_SERVER C:\Programme\VisualSVN Server\ VXIPNPPATHC:\Programme\IVI Foundation\VISA\ gKPDirC:\Programme\gKP\ windirC:\WINDOWS Reporter: Stephan Schwerzmann Labels: jenkins, job, windows New Job - Copy existing Job fails with error Status Code: 500 The job used as source for the copy runs well (our nightly build - hey: it even succeeds :-) The new job is created, but no data is in any of the configuration fields. The new job (empty) can be deleted. Following stacktrace is shown in the Webbrowser: Status Code: 500 Exception: Stacktrace: Warning: Could not find file c:\Daten\Jenkins\.jenkins\jobs\RIMOCTRL_SW_VxWorks-6.7_dev\config.xml to copy. at org.apache.tools.ant.taskdefs.Copy.copySingleFile(Copy.java:573) at org.apache.tools.ant.taskdefs.Copy.execute(Copy.java:403) at hudson.Util.copyFile(Util.java:840) at hudson.model.ItemGroupMixIn.copy(ItemGroupMixIn.java:203) at hudson.model.ItemGroupMixIn.createTopLevelItem(ItemGroupMixIn.java:164) at jenkins.model.Jenkins.doCreateItem(Jenkins.java:2733) at jenkins.model.Jenkins.doCreateItem(Jenkins.java:300) at hudson.model.AllView.doCreateItem(AllView.java:76) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:477) at org.kohsuke.stapler.Stapler.service(Stapler.java:159) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at
[JIRA] (JENKINS-12519) Test Statistic Grid will be rendered diffrently in IE9, Chrome, FF, Opera
[ https://issues.jenkins-ci.org/browse/JENKINS-12519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Ambu reassigned JENKINS-12519: Assignee: Marco Ambu (was: Peter Hayes) Test Statistic Grid will be rendered diffrently in IE9, Chrome, FF, Opera -- Key: JENKINS-12519 URL: https://issues.jenkins-ci.org/browse/JENKINS-12519 Project: Jenkins Issue Type: Bug Components: dashboard-view Environment: jenkins 1.445 dashboard-view 2.1 IE 9, FF 4-10, chrome, opera Reporter: Thomas Fürer Assignee: Marco Ambu Priority: Minor The job names are displayed in a centric style in IE9 and opera but are displyed left bounded in FF and chrome. I would prefer left bounded. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12126) Test Trend Chart should be able to show only the failures
[ https://issues.jenkins-ci.org/browse/JENKINS-12126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Ambu reassigned JENKINS-12126: Assignee: Marco Ambu (was: Peter Hayes) Test Trend Chart should be able to show only the failures - Key: JENKINS-12126 URL: https://issues.jenkins-ci.org/browse/JENKINS-12126 Project: Jenkins Issue Type: New Feature Components: dashboard-view Reporter: Jean-Marc Bourguet Assignee: Marco Ambu The test trend chart in the dashboard view is showing both the number of tests and the number of failures. When you have a big number of tests and few failures, the later aren't visible enough while they are what is important. The test trend chart in the job can be switched to show a graph of only the failure number. A similar graph in the dashboard view would be more useful to me than the current one. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
