[JIRA] [role-strategy-plugin] (JENKINS-18377) Improve the performance when listing many jobs
Title: Message Title
Alexander Ost commented on JENKINS-18377
Re: Improve the performance when listing many jobs
This issue also heavily affects the search box – with role-based auth active (and approx 2500 jobs defined), the search box is barely usable (slow update, long time to feedback). After switching back to matrix-based authentication, the search box works fine.
As previously mentioned, Job-listing is affected as well, but also access to other pages is much slower ("All" view loading takes about twice as long, master node display takes four times longer when RBAC is active).
Running LTS Jenkins 1.609.2.
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] [junit-plugin] (JENKINS-28479) "Latest Test Result" text and "Test Result Trend" plot do not appear for projects which always fail
Title: Message Title Alexander Ost commented on JENKINS-28479 Re: "Latest Test Result" text and "Test Result Trend" plot do not appear for projects which always fail Daniel, we're using a freestyle job to run tests in a custom unit test environment. If _any _of the tests fails, then the run will be marked as FAILED. The junit-plugin is used to display the test results and to provide convenient access to logs etc. Some of this information (trend plot, link to latest test result) are showing up only when there has ever been at least one PASSED or UNSTABLE run – and that's why I created this issue. 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] [junit-plugin] (JENKINS-28479) "Latest Test Result" text and "Test Result Trend" plot do not appear for projects which always fail
Title: Message Title Alexander Ost commented on JENKINS-28479 Re: "Latest Test Result" text and "Test Result Trend" plot do not appear for projects which always fail If there's no successful builds yet, then in all builds at least one test case has failed. In those situations, the trend information is especially useful, since it gives a good indication of how many tests still have to be fixed in order to reach a successful build. Also the "latest test result" link is useful for projects that never passed all tests yet. Typically, you're interested in test logs no matter whether all tests ever passed or not. Both data was available (and appreciated by users : ) before junit-1.2. 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] [core] (JENKINS-10481) Expose fingerprint information from builds in REST API
Title: Message Title Alexander Ost closed an issue as Not A Defect Jenkins / JENKINS-10481 Expose fingerprint information from builds in REST API Change By: Alexander Ost Status: Open Closed Resolution: Not A Defect 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] [core] (JENKINS-10481) Expose fingerprint information from builds in REST API
Title: Message Title
Alexander Ost commented on JENKINS-10481
Re: Expose fingerprint information from builds in REST API
I had the same problem; as Daniel pointed out, this is part of the API already. However, fingerprints are not exposed by default in the REST API.
You need to explicitly set the depth parameter to receive the fingerprints, e.g.
http://myjenkins.local/job/testjob/42/api/xml?depth=2
If you need to retrieve fingerprints only, you can yuse a tree query to avoid ambiguities:
http://myjenkins.local/job/testjob/42/api/xml?depth=2&tree=fingerprint[fileName,hash]{0,}
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] [core] (JENKINS-10481) Expose fingerprint information from builds in REST API
Title: Message Title Alexander Ost assigned an issue to Alexander Ost Jenkins / JENKINS-10481 Expose fingerprint information from builds in REST API Change By: Alexander Ost Assignee: Alexander Ost 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] [job-node-stalker-plugin] (JENKINS-30494) Builds queued despite idle executors, remain in "pending" state for several minutes
Title: Message Title Alexander Ost created an issue Jenkins / JENKINS-30494 Builds queued despite idle executors, remain in "pending" state for several minutes Issue Type: Bug Assignee: Unassigned Components: job-node-stalker-plugin Created: 16/Sep/15 2:09 PM Environment: Jenkins 1.609.2, node-stalker-plugin 1.04, Windows 2008R2/Windows 7 master and (WMI-connected) slaves Labels: jenkins plugin job-node-stalker node-stalker Priority: Major Reporter: Alexander Ost We observe delays of up to several minutes before a job runs, despite idle executors being available. The problem occurs only when the "Share same workspace" option has been selected. It does not appear when the option is disabled. The delay is reproducible. It manifests as follows: the build appears in the build queue, s
[JIRA] [junit-plugin] (JENKINS-28479) "Latest Test Result" text and "Test Result Trend" plot do not appear for projects which always fail
Title: Message Title Alexander Ost commented on JENKINS-28479 Re: "Latest Test Result" text and "Test Result Trend" plot do not appear for projects which always fail The issue is really caused by the SimpleBuildStep migration. The description of the "SimpleBuildStep.LastBuildAction" interface states Marker for explicitly added build actions (as Run.addAction(hudson.model.Action)) which should imply a transient project action (Actionable.getActions()) when present on the Job.getLastSuccessfulBuild(). As getProjectActions() was moved from class JUnitResultArchiver to that interface, the project actions will never become active for jobs that do not contain at least one successful build. The attached patch.txt (for junit-1.6) moves getProjectActions() back to class JUnitResultArchiver, and this fixes the issue. I am not aware of the side-effects of this change, though. Plugin tests are passing as before, but we're not using all features of the plugin. Please, kindly review. 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] [junit-plugin] (JENKINS-28479) "Latest Test Result" text and "Test Result Trend" plot do not appear for projects which always fail
Title: Message Title Alexander Ost updated an issue Jenkins / JENKINS-28479 "Latest Test Result" text and "Test Result Trend" plot do not appear for projects which always fail patch for junit-1.6 that works around the issue Change By: Alexander Ost Attachment: patch.txt 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] [subversion-plugin] (JENKINS-11021) Changelog will ignore peg revisions; whole build fails if peg revision element has disappeared
Title: Message Title Alexander Ost closed an issue as Won't Fix Not sure if the problem still exists. We don't use peg revisions any longer for a long time already. As there's no votes nor watchers, let's close this issue. Jenkins / JENKINS-11021 Changelog will ignore peg revisions; whole build fails if peg revision element has disappeared Change By: Alexander Ost Status: Open Closed Resolution: Won't Fix 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] [junit-plugin] (JENKINS-28479) "Latest Test Result" text and "Test Result Trend" plot do not appear for projects which always fail
Title: Message Title
Alexander Ost created an issue
Jenkins / JENKINS-28479
"Latest Test Result" text and "Test Result Trend" plot do not appear for projects which always fail
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
withOutTrend.png, withTrend.png
Components:
junit-plugin
Created:
19/May/15 12:56 PM
Environment:
Jenkins LTS 1.596.2 / Linux
Priority:
Major
Reporter:
Alexander Ost
Since junit-1.2, neither the "Latest Test Result" information nor the "Test Result Trend" plot appear on the project page if there is not at least one build in non-failed state.
See screenshots below for an example: after deleting unstable build #11, the abovementioned items disappear.
The problem did not exist when the plugin was still included in Jenkins (1.576), nor does it exist in versions 1.0 and 1.1 of the plugin. I suspect that this behaviour was introduced with commit 4ba5a49 ("
[JIRA] [email-ext] (JENKINS-16181) Jenkins does not try to resend a failed e-mail
Alexander Ost reopened JENKINS-16181 Jenkins does not try to resend a failed e-mail Apparently, retry handling for the "connetion refused" case does not yet work properly. I do observe the following stack trace whenever the SMTP server is unreachable: javax.mail.MessagingException: Could not connect to SMTP host: mail.example.net, port: 25; nested exception is: java.net.ConnectException: Connection refused at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1934) at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:638) at javax.mail.Service.connect(Service.java:295) at javax.mail.Service.connect(Service.java:176) at javax.mail.Service.connect(Service.java:125) at javax.mail.Transport.send0(Transport.java:194) at javax.mail.Transport.send(Transport.java:124) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:305) ...but I can never see a "Socket error sending email, retrying once more in 10 seconds" message. I suspect that the root cause is that Transport.send() will not throw a SendFailedException in this case, but rather a MessagingException. However, the plugin code only catches SendFailedException. (Tested with version email-ext-2.37.2.2, but exception type handling is identical on master.) Could you please check? Change By: Alexander Ost (29/Jul/14 8:42 AM) Resolution: Fixed Status: Resolved Reopened 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] [git] (JENKINS-22064) Git Repository Browser URL not saved anymore
Alexander Ost commented on JENKINS-22064 Git Repository Browser URL not saved anymore Nicolas commited a fix yesterday: https://github.com/jenkinsci/git-plugin/commit/b46de67f7f30139f5a876b6f1c6f21fcdbfea821 I cherry-picked that on top of 2.0.4: the correction does solve the issue (with cgit). The browser URL is saved correctly, and the links in the changelog are back. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22064) Git Repository Browser URL not saved anymore
Alexander Ost commented on JENKINS-22064 Git Repository Browser URL not saved anymore This was working fine still with git-plugin version 2.0 and git-client-plugin version 1.6.0. Probably the problem is related to this commit: https://github.com/jenkinsci/git-plugin/commit/7abfafcf58addbce2c268dbfed1910a90d4fe2a3 I'm not enough into Jenkins coding to fix this myself quickly, but Nicolas is already listed as assignee here (thanks!). I hope it's an easy fix. 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] [viewVC] (JENKINS-18283) Wrong URL in diff
Alexander Ost commented on JENKINS-18283 Wrong URL in diff The problem also exists on the LTS branch (1.509.4). Since the pull request is already available, is there any chance to get this released soon? 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-16544) File Leak Detector plugin breaks CLI interface
Alexander Ost
updated JENKINS-16544
File Leak Detector plugin breaks CLI interface
Change By:
Alexander Ost
(30/Jan/13 11:51 AM)
Description:
After activation of the File Leak Detector Plugin via the '
avtivate
activate
' button, the Jenkins CLI stops working:$ java -jar jenkins-cli.jar -s http://myjenkins:8080 helpException in thread "main" java.lang.reflect.UndeclaredThrowableExceptionat $Proxy2.main(Unknown Source)at hudson.cli.CLI.execute(CLI.java:322)at hudson.cli.CLI._main(CLI.java:468)at hudson.cli.CLI.main(CLI.java:373)Caused by: java.io.IOException: Remote call on CLI connection to http://myjenkins:8080 failedat hudson.remoting.Channel.call(Channel.java:673)at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158)... 4 moreCaused by: java.lang.IllegalAccessError: org/kohsuke/args4j/CmdLineParser$1at org.kohsuke.args4j.CmdLineParser.(CmdLineParser.java:94)at hudson.cli.CLICommand.main(CLICommand.java:211)at hudson.cli.CliManagerImpl.main(CliManagerImpl.java:92)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:601)at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:275)at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:256)at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:215)at hudson.remoting.UserRequest.perform(UserRequest.java:118)at hudson.remoting.UserRequest.perform(UserRequest.java:48)at hudson.remoting.Request$2.run(Request.java:326)at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)at hudson.cli.CliManagerImpl$1.call(CliManagerImpl.java:63)at hudson.remoting.InterceptingExecutorService$2.call(InterceptingExecutorService.java:95)at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)at java.util.concurrent.FutureTask.run(FutureTask.java:166)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)at java.lang.Thread.run(Thread.java:722)The corresponding line in args4j::CmdLineParser.java isCollections.sort(options, new Comparator() { public int compare(OptionHandler o1, OptionHandler o2) {return o1.option.toString().compareTo(o2.option.toString()); } });Please have a look - the plugin is really useful, but the CLI is essential.PSI tried to file this issue against the 'file-leak-detector' component, but that doesn't exist. Please forward as appropriate.
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-16544) File Leak Detector plugin breaks CLI interface
Alexander Ost
created JENKINS-16544
File Leak Detector plugin breaks CLI interface
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
30/Jan/13 11:17 AM
Description:
After activation of the File Leak Detector Plugin via the 'avtivate' button, the Jenkins CLI stops working:
$ java -jar jenkins-cli.jar -s http://myjenkins:8080 help
Exception in thread "main" java.lang.reflect.UndeclaredThrowableException
at $Proxy2.main(Unknown Source)
at hudson.cli.CLI.execute(CLI.java:322)
at hudson.cli.CLI._main(CLI.java:468)
at hudson.cli.CLI.main(CLI.java:373)
Caused by: java.io.IOException: Remote call on CLI connection to http://myjenkins:8080 failed
at hudson.remoting.Channel.call(Channel.java:673)
at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158)
... 4 more
Caused by: java.lang.IllegalAccessError: org/kohsuke/args4j/CmdLineParser$1
at org.kohsuke.args4j.CmdLineParser.(CmdLineParser.java:94)
at hudson.cli.CLICommand.main(CLICommand.java:211)
at hudson.cli.CliManagerImpl.main(CliManagerImpl.java:92)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:275)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:256)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:215)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at hudson.cli.CliManagerImpl$1.call(CliManagerImpl.java:63)
at hudson.remoting.InterceptingExecutorService$2.call(InterceptingExecutorService.java:95)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
The corresponding line in args4j::CmdLineParser.java is
Collections.sort(options, new Comparator() {
public int compare(OptionHandler o1, OptionHandler o2) {
return o1.option.toString().compareTo(o2.option.toString());
}
});
Please have a look - the plugin is really useful, but the CLI is essential.
PS
I tried to file this issue against the 'file-leak-detector' component, but that doesn't exist. Please forward as appropriate.
Environment:
jenkins-1.480.1
Linux, Oracle jdk1.7.0_11, headless mode enabled
Project:
Jenkins
Priority:
Major
Reporter:
Alexander Ost
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
[JIRA] (JENKINS-13790) Subversion externals fail
[ https://issues.jenkins-ci.org/browse/JENKINS-13790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163313#comment-163313 ] Alexander Ost commented on JENKINS-13790: - Same here on Linux platform. As a nasty side-effect, also the externals' revision information in /revision.txt is missing. The file only contains the revision of the main repository. > Subversion externals fail > - > > Key: JENKINS-13790 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13790 > Project: Jenkins > Issue Type: Bug > Components: subversion >Affects Versions: current > Environment: Windows XP SP3 >Reporter: chikigai > > Updates on a repository with svn:externals property set fail with the > following: > AssertionError: appears to be using unpatched svnkit at jar:xxx/SVNEvent.class > The issue is present with the latest 1.40 release. > The issue is not preset with the 1.39 release. -- 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-13620) Being able to tone down the enthusiasm of Jenkins towards popping up some contextual menu
[ https://issues.jenkins-ci.org/browse/JENKINS-13620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162603#comment-162603 ] Alexander Ost commented on JENKINS-13620: - I second this -- I used to copy/paste job names frequently from the overview pages. This is no longer possible, and one has to perform two more mouse clicks and wait for several seconds (ie, open the job itself, copy name from title, then go back). To my surprise this seems to bother not only me as Jenkins admin, but also many developers in our team. --> a global configuration flag to disable the menus will be useful --> ideally, a per-user setting will allow to override the global setting > Being able to tone down the enthusiasm of Jenkins towards popping up some > contextual menu > - > > Key: JENKINS-13620 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13620 > Project: Jenkins > Issue Type: Improvement > Components: gui >Affects Versions: current >Reporter: Bruno Mahé > > The new UI improvments and menus are great! > But sometimes it goes a little bit too far. To that end, it would be really > nice if they would be used that much (or providing a way to disable some of > it). > As an example, I have now a great difficulty to select a job name since a > contextual menu keeps on popping up. -- 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
