[JIRA] [performance-plugin] (JENKINS-27100) Regressions in 1.12 and 1.13
Manuel Carrasco commented on JENKINS-27100 Regressions in 1.12 and 1.13 To publish the artefact again I have to increase the version to 1.14, is it ok? I can attach it to this ticket if you can test it before releasing. 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] [performance-plugin] (JENKINS-27100) Regressions in 1.12 and 1.13
Manuel Carrasco commented on JENKINS-27100 Regressions in 1.12 and 1.13 I don't know exactly what is the regression issue, I have tried both compiled and deployed artefacts and they work to me, messages is in the deployed .jar. I don't have enough time to investigate and test all plugin features / issues, so I propose to rollback code to 1.11 unless someone could take the time to collaborate. Any volunteer ? 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] [performance-plugin] (JENKINS-27100) Regressions in 1.12 and 1.13
Manuel Carrasco commented on JENKINS-27100 Regressions in 1.12 and 1.13 Here you have compiled plugin in both formats .jar and .hpi https://drive.google.com/a/alcala.org/folderview?id=0B-VpARgldYW0flhsOFplMlFaRlJ2TlVuNGRGTjI3Mm1OY2NrQzBkLUVFY05HbUFjMXZzLUk# 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] [performance-plugin] (JENKINS-27100) Regressions in 1.12 and 1.13
Manuel Carrasco commented on JENKINS-27100 Regressions in 1.12 and 1.13 Yes I'll do, and will take care that Messages is in the jar before uploading 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] [performance-plugin] (JENKINS-16627) Fail to parse jmeter report
Manuel Carrasco resolved JENKINS-16627 as Fixed Fail to parse jmeter report Change By: Manuel Carrasco (18/Feb/15 10:38 AM) 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/d/optout.
[JIRA] [performance-plugin] (JENKINS-22011) Performance plugin report not failing build based on relative thresholds.
Manuel Carrasco commented on JENKINS-22011 Performance plugin report not failing build based on relative thresholds. @Marko, Can you rebase your patch with the current code. Also if it's possible could you send a pull request in github so as it's easier to review and CI server checks it as well. 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] [performance-plugin] (JENKINS-22011) Performance plugin report not failing build based on relative thresholds.
Manuel Carrasco resolved JENKINS-22011 as Fixed Performance plugin report not failing build based on relative thresholds. Change By: Manuel Carrasco (16/Feb/15 4:34 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/d/optout.
[JIRA] [performance-plugin] (JENKINS-21839) Performance graphs causing Could not initialize class org.jfree.chart.JFreeChart exceptions
Manuel Carrasco closed JENKINS-21839 as Fixed Performance graphs causing Could not initialize class org.jfree.chart.JFreeChart exceptions Not a bug, that happens when running jenkins in a computer with a XServer DISPLAY set. Unset the DISPLAY variable or enable java.awt.headless property. Change By: Manuel Carrasco (18/Feb/14 8:16 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/groups/opt_out.
[JIRA] [performance-plugin] (JENKINS-9031) Performance plugin lock out Jenkins while running Performance Trend
Manuel Carrasco resolved JENKINS-9031 as Fixed Performance plugin lock out Jenkins while running Performance Trend Fixed in git Change By: Manuel Carrasco (10/Jan/14 3:16 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] [performance-plugin] (JENKINS-9031) Performance plugin lock out Jenkins while running Performance Trend
Manuel Carrasco commented on JENKINS-9031 Performance plugin lock out Jenkins while running Performance Trend You are right, I didn't realize that your patch was done with git-diff. Merged: https://github.com/jenkinsci/performance-plugin/commits/master 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] [performance-plugin] (JENKINS-9031) Performance plugin lock out Jenkins while running Performance Trend
Manuel Carrasco commented on JENKINS-9031 Performance plugin lock out Jenkins while running Performance Trend Could you please send a pull-request in github, so as I can merge your contribution easily. 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/groups/opt_out.
[JIRA] [performance-plugin] (JENKINS-9031) Performance plugin lock out Jenkins while running Performance Trend
Manuel Carrasco commented on JENKINS-9031 Performance plugin lock out Jenkins while running Performance Trend Actually it is not difficult at all to me, the thing is that I prefer having you as committer of the patch in git history, and it is the preferred way in Jenkins contributions. I don't have any problem doing it in your way. 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] [performance-plugin] (JENKINS-11359) If you stop a build while syncing to Perforce, the process continues to sync on the build machine.
Manuel Carrasco commented on JENKINS-11359 If you stop a build while syncing to Perforce, the process continues to sync on the build machine. Could you add more info to the report? 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-13370) Logout when trying to set Show only n last builds on Filter trend data page
[ https://issues.jenkins-ci.org/browse/JENKINS-13370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161453#comment-161453 ] Manuel Carrasco commented on JENKINS-13370: --- It seems a problem in the hudson-plugin-info tag used to generate the table with the plugin info. I've asked to the developer mailing list to find a solution. In the meanwhile I've added a note to the page with the correct link Thanks for reporting - Manolo Logout when trying to set Show only n last builds on Filter trend data page --- Key: JENKINS-13370 URL: https://issues.jenkins-ci.org/browse/JENKINS-13370 Project: Jenkins Issue Type: Bug Components: performance-plugin Affects Versions: current Environment: Ubuntu 11.00 Oneiric 64bit OpenJDK 1.7 Reporter: Piotr Czachur Assignee: Manuel Carrasco Priority: Critical Hi! Before I will run into details I just want to say this issue can be a blocker for using performance plugin. If you got hundreds of builds and you cannot make Jenkins to generate trend report for only last N builds you wait hours for images to appear. OK, here are details: When I'm trying to set only n last builds value on Filter trend data page, I get immediately logged out. I've looked into the cookie set by this action and it looks like this: === Name: hudson.plugins.performance Content: BUILD Path: /jenkins/job/mytestjob === There are two side effects here: 1) Setting limit for n last build simply doesn't work 2) After pressing Save button I'm getting immediately logged out and - later - when I try to access build page (mytestjob) I'm also getting logged out. Other jobs' pages work fine. I suspect this has something to do with content of the cookie sent to the server: # cookie sent after setting n last builds limit Cookie: hudson.plugins.performance=BUILD; screenResolution=1920x1080; JSESSIONID=C3EDF6F50798299F696D9387DFC6CBEF # cookie sent by Jenkins in normal conditions (no performance plugin cookie) Cookie: screenResolution=1920x1080; JSESSIONID=C3EDF6F50798299F696D9387DFC6CBEF Cheers! -- 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-13370) Logout when trying to set Show only n last builds on Filter trend data page
[ https://issues.jenkins-ci.org/browse/JENKINS-13370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161453#comment-161453 ] Manuel Carrasco edited comment on JENKINS-13370 at 4/11/12 6:32 AM: Removed wrong comment because it was related to issue JENKINS-13371 was (Author: manolo): It seems a problem in the hudson-plugin-info tag used to generate the table with the plugin info. I've asked to the developer mailing list to find a solution. In the meanwhile I've added a note to the page with the correct link Thanks for reporting - Manolo Logout when trying to set Show only n last builds on Filter trend data page --- Key: JENKINS-13370 URL: https://issues.jenkins-ci.org/browse/JENKINS-13370 Project: Jenkins Issue Type: Bug Components: performance-plugin Affects Versions: current Environment: Ubuntu 11.00 Oneiric 64bit OpenJDK 1.7 Reporter: Piotr Czachur Assignee: Manuel Carrasco Priority: Critical Hi! Before I will run into details I just want to say this issue can be a blocker for using performance plugin. If you got hundreds of builds and you cannot make Jenkins to generate trend report for only last N builds you wait hours for images to appear. OK, here are details: When I'm trying to set only n last builds value on Filter trend data page, I get immediately logged out. I've looked into the cookie set by this action and it looks like this: === Name: hudson.plugins.performance Content: BUILD Path: /jenkins/job/mytestjob === There are two side effects here: 1) Setting limit for n last build simply doesn't work 2) After pressing Save button I'm getting immediately logged out and - later - when I try to access build page (mytestjob) I'm also getting logged out. Other jobs' pages work fine. I suspect this has something to do with content of the cookie sent to the server: # cookie sent after setting n last builds limit Cookie: hudson.plugins.performance=BUILD; screenResolution=1920x1080; JSESSIONID=C3EDF6F50798299F696D9387DFC6CBEF # cookie sent by Jenkins in normal conditions (no performance plugin cookie) Cookie: screenResolution=1920x1080; JSESSIONID=C3EDF6F50798299F696D9387DFC6CBEF Cheers! -- 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-13371) Wrong URL on WIKI for perfformance-plugin bug list.
[ https://issues.jenkins-ci.org/browse/JENKINS-13371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161454#comment-161454 ] Manuel Carrasco commented on JENKINS-13371: --- It seems a problem in the hudson-plugin-info tag used to generate the table with the plugin info. I've asked to the developer mailing list to find a solution. In the meanwhile I've added a note to the page with the correct link Thanks for reporting - Manolo Wrong URL on WIKI for perfformance-plugin bug list. --- Key: JENKINS-13371 URL: https://issues.jenkins-ci.org/browse/JENKINS-13371 Project: Jenkins Issue Type: Bug Components: performance-plugin Reporter: Piotr Czachur Assignee: Manuel Carrasco On Performance Plugin WIKI page (https://wiki.jenkins-ci.org/display/JENKINS/Performance+Plugin) where is URL for Open Issues: http://issues.jenkins-ci.org/secure/IssueNavigator.jspa?mode=hidereset=truejqlQuery=project+%3D+JENKINS+AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%29+AND+component+%3D+%27performance%27 but should be: https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?mode=hidereset=truejqlQuery=project+%3D+JENKINS+AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%29+AND+component+%3D+%27performance-plugin%27 Please update WIKI page. Cheers! -- 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-13370) Logout when trying to set Show only n last builds on Filter trend data page
[ https://issues.jenkins-ci.org/browse/JENKINS-13370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161455#comment-161455 ] Manuel Carrasco commented on JENKINS-13370: --- It seems an issue with the non-closed double quote, I have to check. Logout when trying to set Show only n last builds on Filter trend data page --- Key: JENKINS-13370 URL: https://issues.jenkins-ci.org/browse/JENKINS-13370 Project: Jenkins Issue Type: Bug Components: performance-plugin Affects Versions: current Environment: Ubuntu 11.00 Oneiric 64bit OpenJDK 1.7 Reporter: Piotr Czachur Assignee: Manuel Carrasco Priority: Critical Hi! Before I will run into details I just want to say this issue can be a blocker for using performance plugin. If you got hundreds of builds and you cannot make Jenkins to generate trend report for only last N builds you wait hours for images to appear. OK, here are details: When I'm trying to set only n last builds value on Filter trend data page, I get immediately logged out. I've looked into the cookie set by this action and it looks like this: === Name: hudson.plugins.performance Content: BUILD Path: /jenkins/job/mytestjob === There are two side effects here: 1) Setting limit for n last build simply doesn't work 2) After pressing Save button I'm getting immediately logged out and - later - when I try to access build page (mytestjob) I'm also getting logged out. Other jobs' pages work fine. I suspect this has something to do with content of the cookie sent to the server: # cookie sent after setting n last builds limit Cookie: hudson.plugins.performance=BUILD; screenResolution=1920x1080; JSESSIONID=C3EDF6F50798299F696D9387DFC6CBEF # cookie sent by Jenkins in normal conditions (no performance plugin cookie) Cookie: screenResolution=1920x1080; JSESSIONID=C3EDF6F50798299F696D9387DFC6CBEF Cheers! -- 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-7767) Performance report JMeter not possible to set threshold 0% but 1%
[ https://issues.jenkins-ci.org/browse/JENKINS-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manuel Carrasco resolved JENKINS-7767. -- Fix Version/s: current Resolution: Fixed Performance report JMeter not possible to set threshold 0% but 1% --- Key: JENKINS-7767 URL: https://issues.jenkins-ci.org/browse/JENKINS-7767 Project: Jenkins Issue Type: Bug Components: performance-plugin Affects Versions: current Environment: WINDOWS XP HUDSON Reporter: zillakilla Assignee: Manuel Carrasco Fix For: current When executing jmeter tests within Hudson, Some of the tests fail with an Error% of 0.4% Is it possible to set the thresholds of the Performance Report to a value of less than 1% but greater than 0% ? When entering a value of say 0.1 and saving, the value changes to 0 -- 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
