[JIRA] [ssh] (JENKINS-16235) When running sudo command it gives error sudo: no tty present and no askpass program specified
akash mahakode commented on JENKINS-16235 When running sudo command it gives error sudo: no tty present and no askpass program specified Hi All, I faced the same issue during my development. There is workaround, which always works- If you want run "sudo pwd", then run it as echo "Sudo_password" | sudo -S pwd It will echo the password and give it to sudo and run "pwd" command. Hope it helps. Thanks, Akash Mahakode 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] [slave-squatter] (JENKINS-24449) slave cleanup causes jobs to hang
Christian Goetze commented on JENKINS-24449 slave cleanup causes jobs to hang Probably not, it's "just" a rather nasty slave.jar bug. I can never figure out what tag to use... 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] [core] (JENKINS-24449) slave cleanup causes jobs to hang
Christian Goetze updated JENKINS-24449 slave cleanup causes jobs to hang Change By: Christian Goetze (27/Aug/14 6:26 AM) Component/s: core Component/s: slave-squatter 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] [core] (JENKINS-24455) Font size is broken after upgraded to 1,5,76
Ramkumar Yoganathan created JENKINS-24455 Font size is broken after upgraded to 1,5,76 Issue Type: Bug Assignee: Unassigned Attachments: Jenkins.png Components: core Created: 27/Aug/14 6:32 AM Description: Hi, I upgraded to 1.576 and Jenkins page font was broken all the way that looks ugly. I cleared the browser cache that didn't work. Please let me know Do i need to clean any cache from server end? Thanks, Ram Environment: Windows Server 2012 Project: Jenkins Priority: Major Reporter: Ramkumar Yoganathan 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] [cucumber-testresult] (JENKINS-24456) Name of the component is wrong. Should be cucumber-testresult-plugin, but it's cucumber-testresult
Anatoly Bubenkov created JENKINS-24456 Name of the component is wrong. Should be cucumber-testresult-plugin, but its cucumber-testresult Issue Type: Bug Assignee: teilo Components: cucumber-testresult Created: 27/Aug/14 7:04 AM Description: This leads to always-empty open issues list. Please change Project: Jenkins Priority: Major Reporter: Anatoly Bubenkov 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] [cucumber-testresult] (JENKINS-24457) VERY poor performance on big json files.
Anatoly Bubenkov created JENKINS-24457 VERY poor performance on big json files. Issue Type: Bug Assignee: teilo Components: cucumber-testresult Created: 27/Aug/14 7:06 AM Description: It takes about 20 sec to display any part of the test report when the json file is big enough. Project: Jenkins Priority: Major Reporter: Anatoly Bubenkov 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] [cucumber-testresult] (JENKINS-24457) VERY poor performance on big json files.
teilo commented on JENKINS-24457 VERY poor performance on big json files. Can you be specific on exactly what is slow? Parsing the results in the build? Displaying a feature in the ui? Something else. If it us the display in the ui then 90% chance your jvm heap is too small. Try increasing it and report back. If not please attach a json file that is slow. We observe instant display in a correctly configured system with what i would consider as large features. 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] [cucumber-testresult] (JENKINS-24457) VERY poor performance on big json files.
Anatoly Bubenkov updated JENKINS-24457 VERY poor performance on big json files. Change By: Anatoly Bubenkov (27/Aug/14 7:35 AM) Attachment: FUNCTIONAL-results.json 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] [cucumber-testresult] (JENKINS-24457) VERY poor performance on big json files.
Anatoly Bubenkov commented on JENKINS-24457 VERY poor performance on big json files. Displaying in the ui is the thing which is super slow, parsing, looks OK. I've attached the file. JVM heap size cannot be easily increased because it's already quite optimal... 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] [cucumber-testresult] (JENKINS-24457) VERY poor performance on big json files.
teilo commented on JENKINS-24457 VERY poor performance on big json files. That fule is small. I really urgue you too look at jvmstat when trying to display as I bet you will see lots of gc activity. The plugin loads previous results, but Jenkins stores these in a weak reference and so are the first things to go. So when memory is low loading them up will cause other results to be gced so Jenkins ends up fighting the GC. I will run them through my system but I am expecting instant display. 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] [cucumber-testresult] (JENKINS-24457) VERY poor performance on big json files.
teilo edited a comment on JENKINS-24457 VERY poor performance on big json files. That file is small. I really urgue you too look at jvmstat when trying to display as I bet you will see lots of gc activity. The plugin loads previous results, but Jenkins stores these in a weak reference and so are the first things to go. So when memory is low loading them up will cause other results to be gced so Jenkins ends up fighting the GC. I will run them through my system but I am expecting instant display. 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] [cucumber-testresult] (JENKINS-24457) VERY poor performance on big json files.
teilo commented on JENKINS-24457 VERY poor performance on big json files. If I set a small enough heap I can make a machine spin forever trying to display the results. The same is true to some extent for junit results - but to a lesser degree as the files it loads are smaller. 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] [core] (JENKINS-24458) Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577
Craig Phillips created JENKINS-24458 Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 27/Aug/14 7:54 AM Description: These exceptions are being written to the log file every 5 seconds and thus result in a very large log file. The only work around is to run logrotate every hour, but I still get extremely large log files. Aug 27, 2014 8:49:10 AM org.kohsuke.stapler.export.Property writeValue WARNING: null org.kohsuke.stapler.export.NotExportableException: class org.jenkinsci.plugins.readonly.JobConfiguration doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions at org.kohsuke.stapler.export.Model.init(Model.java:73) at org.kohsuke.stapler.export.ModelBuilder.get(ModelBuilder.java:51) at org.kohsuke.stapler.export.Property.writeValue(Property.java:231) at org.kohsuke.stapler.export.Property.writeValue(Property.java:187) at org.kohsuke.stapler.export.Property.writeValue(Property.java:139) at org.kohsuke.stapler.export.Property.writeTo(Property.java:116) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:190) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Model.writeTo(Model.java:157) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:267) at hudson.model.Api.doXml(Api.java:98) at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at
[JIRA] [cucumber-testresult] (JENKINS-24457) VERY poor performance on big json files.
Anatoly Bubenkov commented on JENKINS-24457 VERY poor performance on big json files. and anatoly@ci-server:~$ free -m total used free sharedbuffers cached Mem: 3954 3680273 0368981 -/+ buffers/cache: 2330 1623 Swap:0 0 0 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] [cucumber-testresult] (JENKINS-24457) VERY poor performance on big json files.
Anatoly Bubenkov commented on JENKINS-24457 VERY poor performance on big json files. ah ok! then which size would you recommend in our situation? http://pastebin.com/pxANWJBE 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] [cucumber-testresult] (JENKINS-24457) VERY poor performance on big json files.
Anatoly Bubenkov edited a comment on JENKINS-24457 VERY poor performance on big json files. and memory http://pastebin.com/1cDeRysb 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-21309) Git plugins changes URL for Bitbucket is incorrect
Jack Wang commented on JENKINS-21309 Git plugins changes URL for Bitbucket is incorrect Any update for this issue? I am having the same problem but my case is a little more complicated as I have jobs using github and bitbucket respectively. commit url for github is correct but not for bitbucket due to the extra "s" in "commits" in url. 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] [cucumber-testresult] (JENKINS-24457) VERY poor performance on big json files.
teilo commented on JENKINS-24457 VERY poor performance on big json files. this file has instant display on my system. I suggest you buy more RAM or upgrade the VM - 4GB is on the small side for a server and you only have 200 free. I would only suggest tuning so you have more young space at the expence of the old if you can not add more ram. 99% usage of the eden is not so good. as an asside - the results are missing timing information - you may want to file a defect against the cucumber-xxx version you are 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 -- 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] [active-directory] (JENKINS-24195) Faster permission lookups when having many unused AD-groups
SCM/JIRA link daemon commented on JENKINS-24195 Faster permission lookups when having many unused AD-groups Code changed in jenkins User: Robert Sandell Path: pom.xml src/main/java/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.java src/main/java/hudson/plugins/active_directory/ActiveDirectoryUserDetail.java src/main/resources/hudson/plugins/active_directory/ActiveDirectorySecurityRealm/config.jelly src/main/resources/hudson/plugins/active_directory/ActiveDirectorySecurityRealm/help-removeIrrelevantGroups.html src/test/java/hudson/plugins/active_directory/RemoveIrrelevantGroupsTest.java http://jenkins-ci.org/commit/active-directory-plugin/90c0688d265eb5ff60e570f4403ea23137a6c92a Log: Merge pull request #10 from fredrikpersson/removegroups JENKINS-24195 Ignoring irrelevant Active Directory groups Compare: https://github.com/jenkinsci/active-directory-plugin/compare/56796545a3e7...90c0688d265e 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] [active-directory] (JENKINS-24195) Faster permission lookups when having many unused AD-groups
SCM/JIRA link daemon commented on JENKINS-24195 Faster permission lookups when having many unused AD-groups Code changed in jenkins User: Fredrik Persson Path: src/main/resources/hudson/plugins/active_directory/ActiveDirectorySecurityRealm/config.jelly http://jenkins-ci.org/commit/active-directory-plugin/962f2c9aab34549c51bc5a093034670b2ef4b385 Log: JENKINS-24195 Added irrelevant group removal for Windows The checkbox for enabling the "Remove irrelevant groups" has been added for Windows based masters 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] [active-directory] (JENKINS-24195) Faster permission lookups when having many unused AD-groups
SCM/JIRA link daemon commented on JENKINS-24195 Faster permission lookups when having many unused AD-groups Code changed in jenkins User: Fredrik Persson Path: pom.xml src/main/java/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.java src/main/java/hudson/plugins/active_directory/ActiveDirectoryUserDetail.java src/main/resources/hudson/plugins/active_directory/ActiveDirectorySecurityRealm/config.jelly src/main/resources/hudson/plugins/active_directory/ActiveDirectorySecurityRealm/help-removeIrrelevantGroups.html src/test/java/hudson/plugins/active_directory/RemoveIrrelevantGroupsTest.java http://jenkins-ci.org/commit/active-directory-plugin/a2561997d3570642415ef1cf880aa29d12b2a17b Log: JENKINS-24195 Ignoring irrelevant Active Directory groups Added an option to make Jenkins ignore Active Directory groups that are not being used by the active Authorization Strategy. This can significantly improve performance in environments with a large number of groups but a small number of corresponding rules defined by the Authorization Strategy. Performance tests have been made in an enviroment with Role Based Authorization Strategy, 7000 jobs and 280 AD groups (where only one of the last groups is used by the AuthorizationStrategy). The average loading time of an empty List View went from 6.2 seconds to 0.2 seconds. An sectioned view with 15 sections of text went from 36 seconds to 0.6 seconds. When Matrix Based Authorization was used instead, loading time of the sectioned view went down from 1.2 seconds to 0.1 seconds. 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] [cucumber-testresult] (JENKINS-24457) VERY poor performance on big json files.
teilo resolved JENKINS-24457 as Not A Defect VERY poor performance on big json files. as per above - not enough free memory causing GC churn on sysytem Change By: teilo (27/Aug/14 8:11 AM) 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 -- 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] [cucumber-testresult] (JENKINS-24457) VERY poor performance on big json files.
Anatoly Bubenkov commented on JENKINS-24457 VERY poor performance on big json files. thanks for all your help! Results are missing timing because producing them is still work-in-progress. We are generating them from pytest-bdd https://github.com/olegpidsadnyi/pytest-bdd#reporting 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] [config-file-provider] (JENKINS-24441) in jenkins (1.577 ) Config File Management plugin in main-panel-content are has ivalid icon path ( double slash before plugin path )
Denis Shvedchenko commented on JENKINS-24441 in jenkins (1.577 ) Config File Management plugin in main-panel-content are has ivalid icon path ( double slash before plugin path ) no, in Manage Jenkins icons displayed correclty as for previous version, i do not remeber 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] [core] (JENKINS-21977) java.io.IOException: Failed to clean up temp dirs because of secret.key
Xu Dony commented on JENKINS-21977 java.io.IOException: Failed to clean up temp dirs because of secret.key I also see this issue when I am trying to run integration tests about workflow plugin on Windows. 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] [unity3d-plugin] (JENKINS-24386) Unity Test Tools package returns 2 or 3 for failed integration testing.
lacostej commented on JENKINS-24386 Unity Test Tools package returns 2 or 3 for failed integration testing. Normally in Jenkins world, one would split the builder (unity3d execution) and the publisher (test collection). The publisher sets the build result: https://github.com/jenkinsci/testng-plugin-plugin/blob/master/src/main/java/hudson/plugins/testng/Publisher.java#L131 I will look into this further. 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] [core] (JENKINS-21977) java.io.IOException: Failed to clean up temp dirs because of secret.key
Dony edited a comment on JENKINS-21977 java.io.IOException: Failed to clean up temp dirs because of secret.key I also encountered this issue when I was trying to run integration tests about workflow plugin on Windows. 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] [core] (JENKINS-24458) Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577
Daniel Beck resolved JENKINS-24458 as Not A Defect Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577 Not a Jenkins core defect. Everything seems to work as intended. Suggestions: File an issue against read-only-configuration that it needs to support being exposed on the Jenkins API Disable and/or uninstall the plugin, and use Extended Read Permission instead Find out who/what does API calls every five seconds (a script you're running or a Jenkins plugin that gathers its data that way, and stop whatever it is (kill the script, disable the plugin, ...). Change By: Daniel Beck (27/Aug/14 8:50 AM) 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 -- 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-24449) slave cleanup causes jobs to hang
Daniel Beck updated JENKINS-24449 slave cleanup causes jobs to hang Change By: Daniel Beck (27/Aug/14 8:52 AM) Labels: remoting 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] [config-file-provider] (JENKINS-24441) in jenkins (1.577 ) Config File Management plugin in main-panel-content are has ivalid icon path ( double slash before plugin path )
Daniel Beck commented on JENKINS-24441 in jenkins (1.577 ) Config File Management plugin in main-panel-content are has ivalid icon path ( double slash before plugin path ) Dominik Bartholdi: I don't use this plugin but if users have a non-empty context path (e.g. /jenkins as used by hpi:run), this doesn't matter only when at the beginning, the double-slash has special meaning. And then you'll actually need to notice the issue, as many browsers will just not display anything instead of the image. If you've never seen it, you won't miss it. 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] [teamconcert] (JENKINS-24459) Jenkins RTC Plugin 1.1.8 doesn't work with Jenkins Version higher then 1.577
Simon Eickel created JENKINS-24459 Jenkins RTC Plugin 1.1.8 doesnt work with Jenkins Version higher then 1.577 Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: BuildDefinitionError.txt Components: teamconcert Created: 27/Aug/14 8:59 AM Description: When upgrading the Jenkins server to version 1.577 and upgrading the TeamConcert Plugin to 1.1.8 a build request won't run anymore triggered from RTC The build failes instead with a credential error message "Invalid password/token for user". After the build failed it isn't possible to test the connection to the Jenkins server in the build engine succesfully. After downgrading the server to 1.575 it's working again. As RTC Build System Toolkit 4.0.6 was used. Please fix this as soon as possible. Greetings, Simon Project: Jenkins Priority: Major Reporter: Simon Eickel 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] [rtc] (JENKINS-24459) Jenkins RTC Plugin 1.1.8 doesn't work with Jenkins Version higher then 1.577
Simon Eickel updated JENKINS-24459 Jenkins RTC Plugin 1.1.8 doesnt work with Jenkins Version higher then 1.577 Change By: Simon Eickel (27/Aug/14 9:00 AM) Labels: concertconfigurationscmserverteam Component/s: rtc 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] [master-slave] (JENKINS-5413) SCM polling getting hung
Daniel Beck commented on JENKINS-5413 SCM polling getting hung sharon xia: That's a completely different issue. This issue is about polling that NEVER finishes, yours aborts after 20 minutes. It even seems to tell you what the problem is: Could not create directory 'c/Users/Administrator/.ssh'. To request further assistance, please ask on the jenkinsci-users mailing list or in #jenkins on Freenode. This thread is long enough already. 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-24454) GIT SCM Pooling hung
Daniel Beck updated JENKINS-24454 GIT SCM Pooling hung Not a core issue, and likely not a Git issue either. Have you tried creating the directory Jenkins fails to create? Or tried Google? Change By: Daniel Beck (27/Aug/14 9:08 AM) Assignee: NicolasDeLoof Component/s: core Component/s: scm-api 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] [core] (JENKINS-24455) Font size is broken after upgraded to 1,5,76
Daniel Beck resolved JENKINS-24455 as Not A Defect Font size is broken after upgraded to 1,5,76 The missing sidepanel images have been addressed in 1.577, and I see nothing else that would be broken. Maybe highlight the specific issue in the screenshot you are referring to? Note that in 1.574, Jenkins started using Helvetica as default font. For advice on reporting problems with recent UI changes, see my comment to JENKINS-24451. Change By: Daniel Beck (27/Aug/14 9:12 AM) 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 -- 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] [teamconcert] (JENKINS-24459) Jenkins RTC Plugin 1.1.8 doesn't work with Jenkins Version higher then 1.577
Daniel Beck updated JENKINS-24459 Jenkins RTC Plugin 1.1.8 doesnt work with Jenkins Version higher then 1.577 Change By: Daniel Beck (27/Aug/14 9:15 AM) Component/s: rtc 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] [core] (JENKINS-20307) Job status page shows Build has been executing for null on master
SCM/JIRA link daemon commented on JENKINS-20307 Job status page shows Build has been executing for null on master Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/Run.java http://jenkins-ci.org/commit/jenkins/fe3b33a16e850f1e5a5fd80b06b3484eb6f4bf98 Log: Merge pull request #1348 from daniel-beck/JENKINS-20307 FIXED JENKINS-20307 Consider OneOffExecutors in Run.getExecutor() Compare: https://github.com/jenkinsci/jenkins/compare/174786b9f758...fe3b33a16e85 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] [core] (JENKINS-20307) Job status page shows Build has been executing for null on master
SCM/JIRA link daemon commented on JENKINS-20307 Job status page shows Build has been executing for null on master Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/Run.java http://jenkins-ci.org/commit/jenkins/9379d1fefc49fbe8cf11bb96290a9924a6eb38cc Log: FIXED JENKINS-20307 Consider OneOffExecutors in Run.getExecutor() 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] [core] (JENKINS-20307) Job status page shows Build has been executing for null on master
SCM/JIRA link daemon resolved JENKINS-20307 as Fixed Job status page shows Build has been executing for null on master Change By: SCM/JIRA link daemon (27/Aug/14 9:18 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24014) Jenkins wrongly(?) warns that reverse proxy set up is broken when using autorefresh link.
SCM/JIRA link daemon resolved JENKINS-24014 as Fixed Jenkins wrongly(?) warns that reverse proxy set up is broken when using autorefresh link. Change By: SCM/JIRA link daemon (27/Aug/14 9:19 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24014) Jenkins wrongly(?) warns that reverse proxy set up is broken when using autorefresh link.
SCM/JIRA link daemon commented on JENKINS-24014 Jenkins wrongly(?) warns that reverse proxy set up is broken when using autorefresh link. Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/diagnosis/ReverseProxySetupMonitor.java http://jenkins-ci.org/commit/jenkins/97366bffe3a7235f8bcd9dfdd30412854ea8308e Log: FIXED JENKINS-24014 Make reverse proxy check tolerate ?auto_refresh 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] [core] (JENKINS-24014) Jenkins wrongly(?) warns that reverse proxy set up is broken when using autorefresh link.
SCM/JIRA link daemon commented on JENKINS-24014 Jenkins wrongly(?) warns that reverse proxy set up is broken when using autorefresh link. Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/diagnosis/ReverseProxySetupMonitor.java http://jenkins-ci.org/commit/jenkins/4b6a8dde7d4b9f09d3a8119ea4c1f15142f259bf Log: Merge pull request #1373 from daniel-beck/JENKINS-24014 FIXED JENKINS-24014 Make reverse proxy check tolerate ?auto_refresh Compare: https://github.com/jenkinsci/jenkins/compare/fe3b33a16e85...4b6a8dde7d4b 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] [core] (JENKINS-24455) Font size is broken after upgraded to 1,5,76
Ramkumar Yoganathan commented on JENKINS-24455 Font size is broken after upgraded to 1,5,76 Thanks for your comment. What is the default font size? Is there any chance to define font size in the config file? Thanks, Ram 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] [cucumber-testresult] (JENKINS-24457) VERY poor performance on big json files.
teilo commented on JENKINS-24457 VERY poor performance on big json files. ahh cool. 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] [core] (JENKINS-24455) Font size is broken after upgraded to 1,5,76
Daniel Beck commented on JENKINS-24455 Font size is broken after upgraded to 1,5,76 The font size is fixed. To change it, you could try to override it using e.g. the Simple Theme plugin, with a bit of CSS you should be able to do that. For further requests for assistance, please ask in #jenkins on Freenode, or on the jenkinsci-users list. 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] [core] (JENKINS-24455) Font size is broken after upgraded to 1,5,76
Ramkumar Yoganathan commented on JENKINS-24455 Font size is broken after upgraded to 1,5,76 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] [cucumber-testresult] (JENKINS-24457) VERY poor performance on big json files.
Daniel Beck commented on JENKINS-24457 VERY poor performance on big json files. Doesn't the free output show that there's plenty of free RAM? The OS would give up caches to applications immediately if needed... 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] [cucumber-testresult] (JENKINS-24456) Name of the component is wrong. Should be cucumber-testresult-plugin, but it's cucumber-testresult
Daniel Beck resolved JENKINS-24456 as Not A Defect Name of the component is wrong. Should be cucumber-testresult-plugin, but its cucumber-testresult This is consistent with all other components in Jira. We're planning to change it soon though, see: https://wiki.jenkins-ci.org/display/JENKINS/2014+JIRA+Components+Refactoring Change By: Daniel Beck (27/Aug/14 9:34 AM) 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 -- 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] [cucumber-testresult] (JENKINS-24457) VERY poor performance on big json files.
Anatoly Bubenkov commented on JENKINS-24457 VERY poor performance on big json files. well, i tried increasing heap size, also increasing young/old ratio, still same issue -Djava.awt.headless=true -Xmx1512m -XX:MaxPermSize=1024m -XX:NewRatio=1 -XX:SurvivorRatio=6 is what i have now any suggestions how to tune it better? 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] [cli] (JENKINS-24385) Jenkins CLI hangs with InvocationTargetException
Daniel Beck commented on JENKINS-24385 Jenkins CLI hangs with InvocationTargetException If the issue still occurs, please run the following in Manage Jenkins » Script Console: Jenkins.getInstance().getExtensionList(hudson.model.PageDecorator.class).get(org.jenkinsci.main.modules.instance_identity.PageDecoratorImpl.class).identity If the result is not null or a NullPointerException, repeat with Jenkins.getInstance().getExtensionList(hudson.model.PageDecorator.class).get(org.jenkinsci.main.modules.instance_identity.PageDecoratorImpl.class) Jenkins.getInstance().getExtensionList(hudson.model.PageDecorator.class) Jenkins.getInstance() (each line as an individual script; not one multi-line script!) Provide output of each. Which version of Jenkins were you using before? 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] [cucumber-testresult] (JENKINS-24457) VERY poor performance on big json files.
Daniel Beck commented on JENKINS-24457 VERY poor performance on big json files. Is this a 32 bit JRE? 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] [cucumber-testresult] (JENKINS-24457) VERY poor performance on big json files.
Anatoly Bubenkov commented on JENKINS-24457 VERY poor performance on big json files. anatoly@ci-server:~$ java -version java version "1.7.0_67" Java(TM) SE Runtime Environment (build 1.7.0_67-b01) Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode) 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] [cucumber-testresult] (JENKINS-24457) VERY poor performance on big json files.
Anatoly Bubenkov commented on JENKINS-24457 VERY poor performance on big json files. @teilo, are you sure there's no issue in the ui code? It looks really strange that we had no issues with other reports... 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] [cucumber-testresult] (JENKINS-24457) VERY poor performance on big json files.
Anatoly Bubenkov commented on JENKINS-24457 VERY poor performance on big json files. root report view: wget 0.00s user 0.00s system 0% cpu 2:40.45 total it's insanely slow... 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] [cucumber-testresult] (JENKINS-24457) VERY poor performance on big json files.
Anatoly Bubenkov commented on JENKINS-24457 VERY poor performance on big json files. i was initially wrong about 20 sec, it's much slower 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] [gui] (JENKINS-23744) Using blanks in names that get parsed to URIs cause URISyntaxException
Tim-Christian Bloss updated JENKINS-23744 Using blanks in names that get parsed to URIs cause URISyntaxException Change By: Tim-Christian Bloss (27/Aug/14 10:29 AM) Environment: DebianGNU/Linux7.5(x64)OracleJRE1.7.0_60Tomcat7.0.54 ADDED2014/08/27:Jenkins1.532.3 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] [core] (JENKINS-20307) Job status page shows Build has been executing for null on master
dogfood commented on JENKINS-20307 Job status page shows Build has been executing for null on master Integrated in jenkins_main_trunk #3651 FIXED JENKINS-20307 Consider OneOffExecutors in Run.getExecutor() (Revision 9379d1fefc49fbe8cf11bb96290a9924a6eb38cc) Result = SUCCESS daniel-beck : 9379d1fefc49fbe8cf11bb96290a9924a6eb38cc Files : core/src/main/java/hudson/model/Run.java 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] [core] (JENKINS-24014) Jenkins wrongly(?) warns that reverse proxy set up is broken when using autorefresh link.
dogfood commented on JENKINS-24014 Jenkins wrongly(?) warns that reverse proxy set up is broken when using autorefresh link. Integrated in jenkins_main_trunk #3651 FIXED JENKINS-24014 Make reverse proxy check tolerate ?auto_refresh (Revision 97366bffe3a7235f8bcd9dfdd30412854ea8308e) Result = SUCCESS daniel-beck : 97366bffe3a7235f8bcd9dfdd30412854ea8308e Files : core/src/main/java/hudson/diagnosis/ReverseProxySetupMonitor.java 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] [core] (JENKINS-24458) Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577
Craig Phillips commented on JENKINS-24458 Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577 It's not just this plugin. It's all of them. And it seems to be related to when Jenkins is sent an ALRM signal. After that, you see these exceptions. Here is another example: org.kohsuke.stapler.export.NotExportableException: class org.jenkinsci.plugins.schedulebuild.ScheduleBuildAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions 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] [core] (JENKINS-24458) Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577
Craig Phillips commented on JENKINS-24458 Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577 And this one org.kohsuke.stapler.export.NotExportableException: class hudson.plugins.depgraph_view.DependencyGraphProjectActionFactory$DependencyGraphProjectAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions and this one org.kohsuke.stapler.export.NotExportableException: class com.sonyericsson.jenkins.plugins.bfa.graphs.ProjectGraphAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions and so on... 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] [core] (JENKINS-24458) Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577
Craig Phillips commented on JENKINS-24458 Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577 The ALRM signal is sent during log rotation to get Jenkins to reopen the log file. After this, Jenkins gets into a mess and just churns out these log entries. As I say, seemed to be fine prior to 1.577. 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] [gui] (JENKINS-23744) Using blanks in names that get parsed to URIs cause URISyntaxException
Tim-Christian Bloss commented on JENKINS-23744 Using blanks in names that get parsed to URIs cause URISyntaxException Sorry, could only select "current version" from dropdown and forgot to mention correct version explicitly. Error occured using Jenkins 1.532.3 (LTS). environment: export LANG=de_DE.UTF-8 Java system.properties set by jsvc invocation: -Duser.language=de -Duser.country=DE -Dfile.encoding=UTF-8 The management/configuration pages said no warnings at all. And there were no errors or warnings visible in the browser while watching those pages which caused these messages. The messages only showed up in the log files. 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] [gerrit] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
rin_ne commented on JENKINS-24445 Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification Why do you manipulate lock file from the external of jenkins instance? it is handled by Jenkins core. So your operation would affect Jenkins itself rather than plugin. I think any plugins has no responsible for this because it is illegal operation. If you want to take enough time until build completed, you can use "sleep SEC" in shell. (For Windows, "timeout /T SEC") 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] [core] (JENKINS-24458) Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577
Craig Phillips reopened JENKINS-24458 Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577 As per my previous comments. It's not related to any single plugin. Change By: Craig Phillips (27/Aug/14 10:48 AM) Resolution: NotADefect 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] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
rogerhu commented on JENKINS-22820 Changes are not commited when using a recent git client I just rechecked with this latest plugin and it works fine on Ubuntu 14.04 and Git 1.9.1. Furthermore, Git 2.1.0 also works fine. I would go to System Log - add a Log recorder for "hudson.plugins.scm_sync_configuration". It should be more obvious what the issue is on your system. Yes, Java 6. Also you can skip setting the parent version (leave it) since there are dependencies going from Hudson to Jenkins. 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] [cli] (JENKINS-24385) Jenkins CLI hangs with InvocationTargetException
Marcel Richter commented on JENKINS-24385 Jenkins CLI hangs with InvocationTargetException I used version 1.532 before. Here the output of each: Jenkins.getInstance().getExtensionList(hudson.model.PageDecorator.class).get(org.jenkinsci.main.modules.instance_identity.PageDecoratorImpl.class).identity java.lang.NullPointerException: Cannot get property 'identity' on null object at org.codehaus.groovy.runtime.NullObject.getProperty(NullObject.java:56) at org.codehaus.groovy.runtime.InvokerHelper.getProperty(InvokerHelper.java:156) at org.codehaus.groovy.runtime.callsite.NullCallSite.getProperty(NullCallSite.java:44) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGetProperty(AbstractCallSite.java:227) at Script1.run(Script1.groovy:1) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:580) . . . Jenkins.getInstance().getExtensionList(hudson.model.PageDecorator.class).get(org.jenkinsci.main.modules.instance_identity.PageDecoratorImpl.class) (No output or empty) Jenkins.getInstance().getExtensionList(hudson.model.PageDecorator.class) Result: [hudson.plugins.jquery.JQuery@2e204881, hudson.plugins.jquery_ui.JQueryUI@497824cf, hudson.model.UpdateCenter$PageDecoratorImpl@6eb8b7b7, hudson.model.DownloadService@2125882b, hudson.model.UsageStatistics@3d7d1983, hudson.plugins.translation.L10nDecorator@601606fe] Jenkins.getInstance() Result: hudson.model.Hudson@47f5435c Seems so as if that PageDecoratorImpl.class object is missing, right? THX 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] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Paul Allen
commented on JENKINS-24028
using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Thanks for the details. Kind of odd why the root is null and the view is missing; I'll look into it.
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] [core] (JENKINS-24458) Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577
Craig Phillips commented on JENKINS-24458 Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577 Actually, it is unrelated to the ALRM signal. It's just all the time. I quieted down Jenkins and restarted the process and straight away the log file is 9.6 MB within a few seconds. I have tried setting the log level to 1, but I am still seeing INFO messages too. How can I disable logging until this is 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] [core] (JENKINS-24458) Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577
Craig Phillips commented on JENKINS-24458 Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577 Just as an idea of how quickly the log is growing: root@d-buildmaster-01 ~# ls -lh /var/log/jenkins/jenkins.log rw-rr- 1 kcc users 9.6M Aug 27 12:10 /var/log/jenkins/jenkins.log root@d-buildmaster-01 ~# ls -lh /var/log/jenkins/jenkins.log rw-rr- 1 kcc users 44M Aug 27 12:11 /var/log/jenkins/jenkins.log 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] [core] (JENKINS-24455) Font size is broken after upgraded to 1,5,76
Ramkumar Yoganathan edited a comment on JENKINS-24455 Font size is broken after upgraded to 1,5,76 Thanks. Could you please let me know which css should i tweak? I was quite happy with previous Verdana and After upgrading to newer version, it looks surprise for me. 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] [core] (JENKINS-24458) Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577
Daniel Beck commented on JENKINS-24458 Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577 The warnings are created because Jenkins cannot serialize some objects in its hierarchy for the API. Find out who calls the API every five seconds and stop that. By default, nothing does that. URLs are different as almost every URL has an API endpoint, but they always end in /api/xml or /api/json, possibly with query string. 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] [core] (JENKINS-24455) Font size is broken after upgraded to 1,5,76
Ramkumar Yoganathan edited a comment on JENKINS-24455 Font size is broken after upgraded to 1,5,76 Thanks. Could you please let me know which css should i tweak? I was quite happy with previous Verdana and After upgrading to newer version, it looks surprise for me. Thanks Got it. War/Css 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] [core] (JENKINS-24458) Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577
Daniel Beck edited a comment on JENKINS-24458 Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577 The warnings are created because Jenkins cannot serialize some objects in its hierarchy for the API. Find out who calls the API every five seconds and stop that. By default, nothing does that. URLs are different as almost every URL has an API endpoint, but they always end in /api/xml or /api/json, possibly with query string. Examples: /job/foo/api/xml?depth=1 /job/foo/lastSuccessfulBuild/api/json 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] [core] (JENKINS-24455) Font size is broken after upgraded to 1,5,76
Ramkumar Yoganathan commented on JENKINS-24455 Font size is broken after upgraded to 1,5,76 This is new my look after changing the CSS font name in War/css/skin.css 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] [core] (JENKINS-24455) Font size is broken after upgraded to 1,5,76
Ramkumar Yoganathan edited a comment on JENKINS-24455 Font size is broken after upgraded to 1,5,76 This is new my look after changing the CSS font name in War/css/skin.css Check NewLook.png Image 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] [core] (JENKINS-24455) Font size is broken after upgraded to 1,5,76
Ramkumar Yoganathan updated JENKINS-24455 Font size is broken after upgraded to 1,5,76 Change By: Ramkumar Yoganathan (27/Aug/14 11:47 AM) Attachment: NewLook.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-flow] (JENKINS-22779) Build-Flow plugin problems in latest version (0.11.1)
brendon wilder commented on JENKINS-22779 Build-Flow plugin problems in latest version (0.11.1) Also experiencing this issue. Plugin 0.12, Jenkins 1.558. None of the following post-build actions work: Trigger Paramaterized, Editable Email, and Build other projects. Enabling 'Flow run needs a workspace' checkbox allows post-build actions to work as expected. 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] [core] (JENKINS-18537) ArrayIndexOutOfBoundsException during Jenkins.doConfigSubmit; need XStream 1.4.6
Kevin Phillips commented on JENKINS-18537 ArrayIndexOutOfBoundsException during Jenkins.doConfigSubmit; need XStream 1.4.6 @Jesse Thanks for pointing that out. You are probably correct. 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-21309) Git plugins changes URL for Bitbucket is incorrect
Mark Waite commented on JENKINS-21309 Git plugins changes URL for Bitbucket is incorrect I had looked inside the source code to see if I could locate the issue from the source code. I was unsuccessful. I hadn't attempted to duplicate the problem from the user interface previously. Today, I tried to duplicate the problem from the user interface. I could not duplicate the problem from the user interface. Could you provide step by step instructions which show how you define the Jenkins job and the clicks you perform to navigate to the URL which contains the extra "s" character? I failed to duplicate the bug with the following steps: Create a new free-style job "JENKINS-21309-bitbucket-url-wrong" Select Git as Source Code Management Insert repository URL https://markewa...@bitbucket.org/git-client-plugin.git Enable SCM polling (so that I can use curl to trigger a poll), no polling schedule is required Cause the repo to poll with "curl http://127.0.0.1:8080/git/notifyCommit?url=""> Confirm the job built based on that poll Submit a change to the repository master branch Cause the repo to poll again with "curl http://127.0.0.1:8080/git/notifyCommit?url=""> Confirm that the job built again and shows the change in the "Recent Changes" I was unable to find any location which linked to a bitbucket diff at all. What link do you click to see a bitbucket diff link, without configuring the bitbucket repository URL in the browser? 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-21309) Git plugins changes URL for Bitbucket is incorrect
Mark Waite commented on JENKINS-21309 Git plugins changes URL for Bitbucket is incorrect If I insert a step into that sequence as step 4.1 which changes the "Repository browser" from "(Auto)" to "bitbucketweb", and insert the URL "https://bitbucket.org/markewaite/git-client-plugin", then I see the correct difference URL when I click "Recent Changes" or "Changes" from the job page. For example, a click on http://127.0.0.1:8080/job/JENKINS-21309-bitbucket-url-wrong/changes shows a page with at least one hyperlink "bitbucketweb". When I click one of those "bitbucketweb" hyperlinks, I'm shown the differences in bitbucketweb. 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-21309) Git plugins changes URL for Bitbucket is incorrect
Mark Waite edited a comment on JENKINS-21309 Git plugins changes URL for Bitbucket is incorrect If I insert a step into that sequence as step 4.1 which changes the "Repository browser" from "(Auto)" to "bitbucketweb", and insert the URL "https://bitbucket.org/markewaite/git-client-plugin", then I see the correct difference URL when I click "Recent Changes" or "Changes" from the job page. For example, a click on http://127.0.0.1:8080/job/JENKINS-21309-bitbucket-url-wrong/changes shows a page with at least one hyperlink "bitbucketweb". When I click one of those "bitbucketweb" hyperlinks, I'm shown the differences in bitbucketweb. The differences URL opened by the browser is https://bitbucket.org/markewaite/git-client-plugin/commits/ee41656ad8ef9b371e4130ec10489803907b57f0 (note that it includes "commits" in the URL) 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] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
David Cullen commented on JENKINS-22820 Changes are not commited when using a recent git client The problem is that the scm-sync-plugin no longer supports git+ssh URIs: ssh: Could not resolve hostname git%2bssh: Name or service not known After I removed the "git+" from the URI, the plugin worked with git 1.9.1. I still do not get commit message dialogs. Will I be able to debug that using the setup in your blog post? Also, what JDK should I install? I think that Java 7 was installed because I used the PPA to install Jenkins and it pulled in the default JRE during the install. 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] [gerrit] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
Martin Schröder
commented on JENKINS-24445
Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
Hi Rinrin.
The lockfile has nothing to do with Jenkins. It is merely a file, that the Jenkins Bash Build Step is waiting for, precisely NOT to need to use a fixed sleep time.
This is used to let specific builds of "Test_1" and "Test_2" finish in the desired order, by deleting the "lock files" in the appropriate order. The Bash build step looks like that:
{{#!bash
Write out a lock file, that delays, until it is deleted
lck="LOCKFILE-${JOB_NAME}-${BUILD_NUMBER}"
echo "Creating file and waiting for deletion of it: $lck"
touch "$lck"
while [[ -e "$lck" ]]; do
sleep 1
done
exit 1}}
It is easy to see, that this buildstep looks like a totally normal build, to both Jenkins and the Gerrit Trigger plugin. It's just a shell build step that is taking some user-defined amount of time.
Thus, the only change over a normal "sleep time" is that you, as the debugger, can select the exact order in which these build steps will return.
You can easily change this to a fixed timeout, but that way, you need to be either quick about re-triggering the builds, or make the timeout so long, that you're needlessly waiting for the tests to end.
In any case, the bug is fully and wholly independent of what the build step does. It only matters in which order they return and that the retriggering happens WHILE the previously triggered tests are still running.
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] [core] (JENKINS-24458) Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577
Craig Phillips commented on JENKINS-24458 Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577 I am calling the API. I have automatic job maintenance that uses the CLI to remove and add jobs associated with branches. It's been working fine until now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24458) Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577
Craig Phillips commented on JENKINS-24458 Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577 We also have a radiator written in _javascript_. It displays the photographs of culprits obtained from LDAP. We hook into the job API's to obtain the breakers and build states. Again, something we have done for months with no problems. 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] [gerrit] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
Martin Schröder
edited a comment on JENKINS-24445
Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
Hi Rinrin.
The lockfile has nothing to do with Jenkins. It is merely a file, that the Jenkins Bash Build Step is waiting for, precisely NOT to need to use a fixed sleep time.
This is used to let specific builds of "Test_1" and "Test_2" finish in the desired order, by deleting the "lock files" in the appropriate order. The Bash build step looks like that:
#!bash
# Write out a lock file, that delays, until it is deleted
lck="LOCKFILE-${JOB_NAME}-${BUILD_NUMBER}"
echo "Creating file and waiting for deletion of it: $lck"
touch "$lck"
while [[ -e "$lck" ]]; do
sleep 1
done
exit 1
It is easy to see, that this buildstep looks like a totally normal build, to both Jenkins and the Gerrit Trigger plugin. It's just a shell build step that is taking some user-defined amount of time.
Thus, the only change over a normal "sleep time" is that you, as the debugger, can select the exact order in which these build steps will return.
You can easily change this to a fixed timeout, but that way, you need to be either quick about re-triggering the builds, or make the timeout so long, that you're needlessly waiting for the tests to end.
In any case, the bug is fully and wholly independent of what the build step does. It only matters in which order they return and that the retriggering happens WHILE the previously triggered tests are still running.
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] [core] (JENKINS-24458) Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577
Craig Phillips commented on JENKINS-24458 Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577 I have modified the init.d script and sysconfig to support a JENKINS_LOGFILE and JENKINS_WEBROOT option. This has allowed me to redirect the logging to /dev/null for now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24460) (new) externals checkout failure (No Credential to try)
Tom Ghyselinck created JENKINS-24460 (new) externals checkout failure (No Credential to try) Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: subversion Created: 27/Aug/14 12:38 PM Description: We have a project which added a new external reference. This external reference has an external reference at his point too. MyProject build-scripts (X) binutils (X) split-debug The update fails when the binutils has been added since the previous build. I don't know if the second external reference is relevant, but I added for convenience to show the specific configuration at our site. The reason this is a Critical issues is because we have many multi-configuration Jobs, building the same project for multiple target platforms. When we add a new external reference, it takes a few builds (and a lot of time) until all Jobs for all platforms have been rebuilt back to success. Fetching 'svn+ssh://subversion.company.com/binutils/branches/1.x/build-scripts' at -1 into '/path/to/MyProject/build-scripts/binutils' AUbuild-scripts/binutils/split-debug Ubuild-scripts/binutils Fetching 'svn+ssh://subversion.company.com/splitdebug' at -1 into '/path/to/MyProject/build-scripts/binutils/splitdebug' AUbuild-scripts/binutils/splitdebug/isolated-functions.sh AUbuild-scripts/binutils/splitdebug/prepstrip At revision 34 At revision 8 ... hudson.util.IOException2: revision check failed on svn+ssh://subversion.company.com/binutils/branches/1.x/build-scripts at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:191) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:132) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:735) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:873) at hudson.model.AbstractProject.checkout(AbstractProject.java:1252) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:615) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:524) at hudson.model.Run.execute(Run.java:1706) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:232) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185) at org.tmatesoft.svn.core.internal.io.svn.SVNSSHConnector.open(SVNSSHConnector.java:77) at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.open(SVNConnection.java:77) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:1252) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.getLatestRevision(SVNRepositoryImpl.java:168) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:967) at
[JIRA] [subversion] (JENKINS-24460) (new) externals checkout failure (No Credential to try)
Daniel Beck commented on JENKINS-24460 (new) externals checkout failure (No Credential to try) Did you read and follow the instructions in JENKINS-21785 and ALL its comments? 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] [core] (JENKINS-24458) Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577
Daniel Beck commented on JENKINS-24458 Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577 The API calls resulting in these exceptions do not actually produce JSON/XML output, so that's not a real solution for you. Since you're writing that it's been "working fine until now" I have to ask: what changed? Jenkins update? If so, from which version to 1.577? Plugins installed? Updated? If so, which? "It's not just this plugin. It's all of them" seems like an exaggeration could you provide the list of plugins (or classes/fields from the first line of the exception message) affected here? A possible workaround restoring functionality would be in looking to filter API output, e.g. the XML API has an argument "tree" that allows you to only retrieve a subset of fields. 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-24454) GIT SCM Pooling hung
Mark Waite commented on JENKINS-24454 GIT SCM Pooling hung You might review this stackoverflow posting for ideas of things you might try. It is not exactly the same case, but it was one of the first items when I searched google with that error message. 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] [subversion] (JENKINS-24460) (new) externals checkout failure (No Credential to try)
Tom Ghyselinck
updated JENKINS-24460
(new) externals checkout failure (No Credential to try)
Change By:
Tom Ghyselinck
(27/Aug/14 12:51 PM)
Description:
Wehaveaprojectwhichaddedanewexternalreference
betweentwobuilds
.
_*Note*_:
Thisexternalreferencehasanexternalreferenceathispointtoo.{{MyProject}}-{{build-scripts}}--(X){{binutils}}---(X){{split-debug}}Theupdatefailswhenthe_{{binutils}}_hasbeenaddedsincethepreviousbuild.Idontknowifthe_secondexternalreference_isrelevant,butIaddedforconveniencetoshowthespecificconfigurationatoursite.Thereasonthisisa
_Critical_
_*Critical*_
issuesisbecausewehavemany
_*
multi-configurationJobs
*_with_*touchstonebuilds*_defined
,buildingthesameprojectformultipletargetplatforms.Whenweaddanewexternalreference,ittakes_*afewbuilds*_(andalotoftime)until_*allJobs*_for_*allplatforms*_havebeen_*rebuiltbackto
success
normal
*_
.
:
#Rebuild1:_mainJob_isnowbacktonormal,but_touchstonebuilds_nowfail
#Rebuild2:_touchstonebuilds_nowbacktonormal,_remaining_Jobsfail#Rebuild3:_remaining_Jobsnowbacktonormal
{quote}Fetchingsvn+ssh://subversion.company.com/binutils/branches/1.x/build-scriptsat-1into/path/to/MyProject/build-scripts/binutilsAUbuild-scripts/binutils/split-debugUbuild-scripts/binutilsFetchingsvn+ssh://subversion.company.com/splitdebugat-1into/path/to/MyProject/build-scripts/binutils/splitdebugAUbuild-scripts/binutils/splitdebug/isolated-functions.shAUbuild-scripts/binutils/splitdebug/prepstripAtrevision34Atrevision8{quote}...{quote}hudson.util.IOException2:revisioncheckfailedonsvn+ssh://subversion.company.com/binutils/branches/1.x/build-scripts athudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:191) athudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:132) athudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:735) athudson.scm.SubversionSCM.checkout(SubversionSCM.java:873) athudson.model.AbstractProject.checkout(AbstractProject.java:1252) athudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:615) atjenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:524) athudson.model.Run.execute(Run.java:1706) athudson.matrix.MatrixRun.run(MatrixRun.java:146) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:232)Causedby:org.tmatesoft.svn.core.SVNCancelException:svn:E200015:Nocredentialtotry.Authenticationfailed atorg.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) atorg.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) atorg.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185) atorg.tmatesoft.svn.core.internal.io.svn.SVNSSHConnector.open(SVNSSHConnector.java:77) atorg.tmatesoft.svn.core.internal.io.svn.SVNConnection.open(SVNConnection.java:77) atorg.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:1252) atorg.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.getLatestRevision(SVNRepositoryImpl.java:168) atorg.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) atorg.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) atorg.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) atorg.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) atorg.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) atorg.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) atorg.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) atorg.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) atorg.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:967) atorg.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:872) athudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:179) ...11more{quote}
[JIRA] [gerrit] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
Martin Schröder updated JENKINS-24445 Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification Change By: Martin Schröder (27/Aug/14 12:52 PM) Environment: OperatingSystemindependent(verifiedonLinuxaswellas Unix Windows )Testedin3latestJenkinsLTSreleases(1.509,1.532and1.554) 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] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Paul Allen
commented on JENKINS-24028
using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Thinking about this; Manual mode was the only one I intended to use for variable expansion ${foo} in the View. However, Template and Streams were the modes I had thought would be used for slave/matrix builds.
As you can see the View is expanded for the Parent as I would expect, but the workspace is assumed to have already been created for the children and so the fields are blank.
I could enhance the plugin to either:
1. Support view expansion for template workspaces (not possible for streams as the View is managed by the server).
or
2. For manual builds, auto create workspaces for the children at build time.
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] [core] (JENKINS-24458) Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577
Craig Phillips commented on JENKINS-24458 Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577 I'll try and satisfy all your requests. Starting with the first question "what changed?". I upgraded to 1.576 to see if another bug I raised (File descriptor leaks) had been resolved. The original issue had been resolved and now I don't have to have a Jenkins job running to monitor the number of open file descriptors, forcing a graceful restart before it hits the limit and crashes. However, upgrading introduced the issue with the "//" double slash preceding icon paths for plugin icons. This resulted in lengthy loading times for every page, while the browser tried to resolve "//plugin" as a host name. I eagerly awaited 1.577 and upgraded as soon as it was available. It resolved the icon path issue, but has now introduced this problem. I don't normally just decide to upgrade at random. I upgrade if I require something from some issue I have logged. As part of the upgrade, I upgraded all plugins installed to their latest versions: /pluginManager/api/xml?depth=2xpath=//plugin/*name()%20=%20%27shortName%27%20or%20name()%20=%20%27version%27wrapper=root root shortNameanalysis-core/shortName version1.58/version shortNamecvs-tag/shortName version1.7/version shortNameall-changes/shortName version1.3/version shortNametoken-macro/shortName version1.10/version shortNamemaven-plugin/shortName version2.6/version shortNamepurge-build-queue-plugin/shortName version1.0/version shortNamecredentials/shortName version1.16.1/version shortNamegit/shortName version2.2.5/version shortNamejna-native-support-plugin/shortName version3.0.4/version shortNameschedule-build/shortName version0.3.3/version shortNamescripttrigger/shortName version0.31/version shortNamebuild-publisher/shortName version1.19/version shortNamejunit/shortName version1.1/version shortNamecobertura/shortName version1.9.5/version shortNamehtmlpublisher/shortName version1.3/version shortNamedepgraph-view/shortName version0.11/version shortNameant/shortName version1.2/version shortNamemapdb-api/shortName version1.0.1.0/version shortNamegit-client/shortName version1.10.1/version shortNameviolations/shortName version0.7.11/version shortNamews-cleanup/shortName version0.22/version shortNamepam-auth/shortName version1.2/version shortNamegroovy/shortName version1.20/version shortNamejavadoc/shortName version1.2/version shortNamexfpanel/shortName version1.2.2/version shortNameviewVC/shortName version1.7/version shortNamegreenballs/shortName version1.14/version shortNamerun-condition/shortName version1.0/version shortNamenunit/shortName version0.16/version shortNameemail-ext/shortName version2.38.1/version shortNameread-only-configurations/shortName version1.10/version shortNameldap/shortName version1.10.2/version shortNamefiles-found-trigger/shortName version1.3/version shortNameparameterized-trigger/shortName version2.25/version shortNamedoclinks/shortName version0.6/version shortNamessh-credentials/shortName version1.9/version shortNamedashboard-view/shortName version2.9.4/version shortNamejquery/shortName version1.7.2-1/version shortNamebuildresult-trigger/shortName version0.17/version shortNamejquery-ui/shortName version1.0.2/version shortNamecopyartifact/shortName version1.31/version shortNamebuildgraph-view/shortName version1.1.1/version shortNamechanges-since-last-success/shortName version0.5/version shortNamePrioritySorter/shortName version2.8/version shortNamedisplay-upstream-changes/shortName version0.1/version shortNamejfreechart-plugin/shortName version1.5/version shortNamecvs/shortName version2.12/version shortNamerole-strategy/shortName version2.2.0/version shortNamebuild-failure-analyzer/shortName version1.9.1/version shortNamemailer/shortName version1.11/version shortNameexternal-monitor-job/shortName version1.2/version shortNamefstrigger/shortName version0.39/version shortNametranslation/shortName version1.11/version shortNameview-job-filters/shortName version1.26/version shortNameantisamy-markup-formatter/shortName version1.2/version shortNamebuild-pipeline-plugin/shortName version1.4.3/version shortNameurltrigger/shortName version0.37/version shortNamewindows-slaves/shortName version1.0/version shortNamematrix-auth/shortName version1.2/version shortNamessh-slaves/shortName version3.0.2/version shortNamedelivery-pipeline-plugin/shortName version0.8.5/version shortNamematrix-project/shortName version1.3/version
[JIRA] [gerrit] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
Martin Schröder
updated JENKINS-24445
Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
Change By:
Martin Schröder
(27/Aug/14 1:08 PM)
Description:
ThereisaseriousissuewiththeGerrittriggerpluginanditsretriggerfunctionality.Thisissuecausestheplugintogetconfusedabouthowmanyandwhichbuildsitstartedforaparticularchangeset/patchsetcombination
,and
Thiscausesitto
decidetoposttheVerificationorCodeReviewupdate
*
evenifnotalltesthavepassedyet
*
.ThisbehaviourleadstoinconsistentverificationresultsinGerritandcanbeeasilyreplicatedasfollows:
1.)
#
Startablank,vanillaJenkinsserverofanarbitraryversiononyourlocalhost(thejobsbelowassumethataBASHshellisavailable).
2.)
#
Installthegerrit-triggerplugin(arbitraryversion,asallareaffected)
3.)
#
Increasetheexecutorcountofthemasternodetoatleast6.
4.)
#
RestarttheserverandcreateaconnectiontoaGerritservice.
5.)
#
Shutdowntheserverandextractthetwojobs(Test_1andTest_2)intothejobsdirectoryoftheJenkinsserver.
5.a)
#*
Test_1willalwaysfail,Test_2willalwayssucceed.Bothwillcreatealock-filenamedLOCKFILE-$
\
{JOB_NAME}-$
\
{BUILD_NUMBER}in$
\
{JENKINS_HOME}/workspace/Centralandwaitforittobedeleted,beforesucceedingorfailing.
6.)
#
(Optional)AltertheTest_1andTest_2
parameters
GerritTriggersettings
tolistentoaspecificrepository.Bydefault
,both
repoandbrancharesetto**.
\\
Afterthisset-upisdone,uploadapatchsettotheGerritservice
inquestion
thatyouconfiguredJenkinstolistento
.ThiswillcauseabuildofTest_1andTest_2tobestarted.
Now,
*
whiletheyarerunning
*
(
rememberthat
they
are
will
waituntilyoudeletetheirlock-file),gointothemanualtriggerinterface:http://[jenkins]/gerrit_manual_trigger/?Searchforthechangesetandissuea
*
retrigger
*
.Thiswillcausetwoadditionalbuildstospawn,oneforTest_1andoneforTest_2.Nowthat4testsarerunning,thecorrectbehaviouroftheGerrittriggerpluginistoignorethefirsttworunsthathavebeenstartedbythePatchsetCreatedevent.Instead,itshouldwaituntilBOTHoftheretriggeredbuildshavefinishedandthenuploadaVerified-1messagetoGerrit.Totestthis,firstdeletethetwooriginallockfiles:$
\
{JENKINS_HOME}/workspace/Central/LOCKFILE-Test_1-1$
\
{JENKINS_HOME}/workspace/Central/LOCKFILE-Test_2-1Thisteststhefirsthalfoftheproblem.Thisworksfine.Afterbothhavefinished,theGerritTriggerpluginwillstillwaitforthe
others
othertwojobs
tofinish.Now,toexposethebug,
*
ONLY
*
deletethelockfileforthe
retriggered
re-triggered
TEST_2job:$
\
{JENKINS_HOME}/workspace/Central/LOCKFILE-Test_2-2ThiswillletTest_2finishsuccessfully(asTest_2alwayssucceeds).
*
Thebugthathappensnow
is
,
is
thatthetriggerpluginuploadsaVerified+1message,DESPITETest_1#2notyetbeingfinished.
*
IfyouthenalsoletTest_1finish,ituploadsyetanotherverification,thistimeVerified-1.Thisbehaviouris
absolutely
_absolutely_
wrong,asitsendsaverificationstatewithoutwaitingforalljobstocomplete,thusleadingto
*
inconsistentresults
*
inGerrit.HeresanexcerptofhowthisbehaviourlookslikeinGerrit:
{noformat}
##JenkinsPatchSet1:-VerifiedBuildStartedTest_2/1/(1/2)---JenkinsPatchSet1:BuildStartedTest_1/1/(2/2)---JenkinsPatchSet1:BuildStartedTest_2/2/(2/2)---JenkinsPatchSet1:BuildStartedTest_1/2/(2/2)---JenkinsPatchSet1:Verified+1BuildSuccessfulTest_2/2/:SUCCESS---JenkinsPatchSet1:Verified-1BuildFailedTest_1/2/:FAILURE##
{noformat}
Youcanseetwobugsatworkhere:1.)Theplugingetsconfusedwhencountingthenumberofjobsstarted2.)Theplugindoesnotwaitfor(Test_1#2)after(Test_2#2)hasfinished.
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
[JIRA] [gerrit] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
Martin Schröder
updated JENKINS-24445
Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
Change By:
Martin Schröder
(27/Aug/14 1:13 PM)
Description:
ThereisaseriousissuewiththeGerrittriggerpluginanditsretriggerfunctionality.
h4.Problem
Thisissuecausestheplugintogetconfusedabouthowmanyandwhichbuildsitstartedforaparticularchangeset/patchsetcombination
ThiscausesittodecidetoposttheVerificationorCodeReviewupdate*evenifnotalltesthavepassedyet*
.ThisbehaviourleadstoinconsistentverificationresultsinGerrit
andcanbeeasilyreplicatedasfollows:
,because*itfailswaitforallteststocomplete.*
h4.Replicationinstructions
#Startablank,vanillaJenkinsserverofanarbitraryversiononyourlocalhost(thejobsbelowassumethataBASHshellisavailable).#Installthegerrit-triggerplugin(arbitraryversion,asallareaffected)#Increasetheexecutorcountofthemasternodetoatleast6.#RestarttheserverandcreateaconnectiontoaGerritservice.#Shutdowntheserverandextractthetwojobs(Test_1andTest_2)intothejobsdirectoryoftheJenkinsserver.#*Test_1willalwaysfail,Test_2willalwayssucceed.Bothwillcreatealock-filenamedLOCKFILE-$\{JOB_NAME}-$\{BUILD_NUMBER}in$\{JENKINS_HOME}/workspace/Centralandwaitforittobedeleted,beforesucceedingorfailing.#(Optional)AltertheTest_1andTest_2GerritTriggersettingstolistentoaspecificrepository.Bydefault,bothrepoandbrancharesetto**.\\Afterthisset-upisdone,uploadapatchsettotheGerritservicethatyouconfiguredJenkinstolistento.ThiswillcauseabuildofTest_1andTest_2tobestarted.Now,*whiletheyarerunning*(rememberthattheywillwaituntilyoudeletetheirlock-file),gointothemanualtriggerinterface:http://[jenkins]/gerrit_manual_trigger/?Searchforthechangesetandissuea*retrigger*.Thiswillcausetwoadditionalbuildstospawn,oneforTest_1andoneforTest_2.Nowthat4testsarerunning,thecorrectbehaviouroftheGerrittriggerpluginistoignorethefirsttworunsthathavebeenstartedbythePatchsetCreatedevent.Instead,itshouldwaituntilBOTHoftheretriggeredbuildshavefinishedandthenuploadaVerified-1messagetoGerrit.Totestthis,firstdeletethetwooriginallockfiles:$\{JENKINS_HOME}/workspace/Central/LOCKFILE-Test_1-1$\{JENKINS_HOME}/workspace/Central/LOCKFILE-Test_2-1Thisteststhefirsthalfoftheproblem.Thisworksfine.Afterbothhavefinished,theGerritTriggerpluginwillstillwaitfortheothertwojobstofinish.Now,toexposethebug,*ONLY*deletethelockfileforthere-triggeredTEST_2job:$\{JENKINS_HOME}/workspace/Central/LOCKFILE-Test_2-2ThiswillletTest_2finishsuccessfully(asTest_2alwayssucceeds).*Thebugthathappensnow,isthatthetriggerpluginuploadsaVerified+1message,DESPITETest_1#2notyetbeingfinished.*IfyouthenalsoletTest_1finish,ituploadsyetanotherverification,thistimeVerified-1.Thisbehaviouris_absolutely_wrong,asitsendsaverificationstatewithoutwaitingforalljobstocomplete,thusleadingto*inconsistentresults*inGerrit.
h4.ExampleoutputinGerrit,whenerroroccurs
HeresanexcerptofhowthisbehaviourlookslikeinGerrit:{noformat}##JenkinsPatchSet1:-VerifiedBuildStartedTest_2/1/(1/2)---JenkinsPatchSet1:BuildStartedTest_1/1/(2/2)---JenkinsPatchSet1:BuildStartedTest_2/2/(2/2)---JenkinsPatchSet1:BuildStartedTest_1/2/(2/2)---JenkinsPatchSet1:Verified+1BuildSuccessfulTest_2/2/:SUCCESS---JenkinsPatchSet1:Verified-1BuildFailedTest_1/2/:FAILURE##{noformat}Youcanseetwobugs
outlineabove
atworkhere:1.)Theplugingetsconfusedwhencountingthenumberofjobsstarted2.)Theplugindoesnotwaitfor(Test_1#2)after(Test_2#2)hasfinished.
[EDIT:Improvedtextformatting.Nowthereportismorethanjustawalloftext]
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] [gerrit] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
Martin Schröder
updated JENKINS-24445
Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
Change By:
Martin Schröder
(27/Aug/14 1:17 PM)
Description:
ThereisaseriousissuewiththeGerrittriggerpluginanditsretriggerfunctionality.h4.ProblemThisissuecausestheplugintogetconfusedabouthowmanyandwhichbuildsitstartedforaparticularchangeset/patchsetcombination.ThisbehaviourleadstoinconsistentverificationresultsinGerrit,because*itfails
to
waitforallteststocomplete.*h4.Replicationinstructions#Startablank,vanillaJenkinsserverofanarbitraryversiononyourlocalhost(thejobsbelowassumethataBASHshellisavailable).#Installthegerrit-triggerplugin(arbitraryversion,asallareaffected)#Increasetheexecutorcountofthemasternodetoatleast6.#RestarttheserverandcreateaconnectiontoaGerritservice.#Shutdowntheserverandextractthetwojobs(Test_1andTest_2)intothejobsdirectoryoftheJenkinsserver.#*Test_1willalwaysfail,Test_2willalwayssucceed.Bothwillcreatealock-filenamedLOCKFILE-$\{JOB_NAME}-$\{BUILD_NUMBER}in$\{JENKINS_HOME}/workspace/Centralandwaitforittobedeleted,beforesucceedingorfailing.#(Optional)AltertheTest_1andTest_2GerritTriggersettingstolistentoaspecificrepository.Bydefault,bothrepoandbrancharesetto**.\\Afterthisset-upisdone,uploadapatchsettotheGerritservicethatyouconfiguredJenkinstolistento.ThiswillcauseabuildofTest_1andTest_2tobestarted.Now,*whiletheyarerunning*(rememberthattheywillwaituntilyoudeletetheirlock-file),gointothemanualtriggerinterface:http://[jenkins]/gerrit_manual_trigger/?Searchforthechangesetandissuea*retrigger*.Thiswillcausetwoadditionalbuildstospawn,oneforTest_1andoneforTest_2.Nowthat4testsarerunning,thecorrectbehaviouroftheGerrittriggerpluginistoignorethefirsttworunsthathavebeenstartedbythePatchsetCreatedevent.Instead,itshouldwaituntilBOTHoftheretriggeredbuildshavefinishedandthenuploadaVerified-1messagetoGerrit.Totestthis,firstdeletethetwooriginallockfiles:$\{JENKINS_HOME}/workspace/Central/LOCKFILE-Test_1-1$\{JENKINS_HOME}/workspace/Central/LOCKFILE-Test_2-1Thisteststhefirsthalfoftheproblem.Thisworksfine.Afterbothhavefinished,theGerritTriggerpluginwillstillwaitfortheothertwojobstofinish.Now,toexposethebug,*ONLY*deletethelockfileforthere-triggeredTEST_2job:$\{JENKINS_HOME}/workspace/Central/LOCKFILE-Test_2-2ThiswillletTest_2finishsuccessfully(asTest_2alwayssucceeds).*Thebugthathappensnow,isthatthetriggerpluginuploadsaVerified+1message,DESPITETest_1#2notyetbeingfinished.*IfyouthenalsoletTest_1finish,ituploadsyetanotherverification,thistimeVerified-1.Thisbehaviouris_absolutely_wrong,asitsendsaverificationstatewithoutwaitingforalljobstocomplete,thusleadingto*inconsistentresults*inGerrit.h4.ExampleoutputinGerrit,whenerroroccursHeresanexcerptofhowthisbehaviourlookslikeinGerrit:{noformat}##JenkinsPatchSet1:-VerifiedBuildStartedTest_2/1/(1/2)---JenkinsPatchSet1:BuildStartedTest_1/1/(2/2)---JenkinsPatchSet1:BuildStartedTest_2/2/(2/2)---JenkinsPatchSet1:BuildStartedTest_1/2/(2/2)---JenkinsPatchSet1:Verified+1BuildSuccessfulTest_2/2/:SUCCESS---JenkinsPatchSet1:Verified-1BuildFailedTest_1/2/:FAILURE##{noformat}Youcanseetwobugsoutlineaboveatworkhere:1.)Theplugingetsconfusedwhencountingthenumberofjobsstarted2.)Theplugindoesnotwaitfor(Test_1#2)after(Test_2#2)hasfinished.[EDIT:Improvedtextformatting.Nowthereportismorethanjustawalloftext]
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
[JIRA] [core] (JENKINS-24458) Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577
Daniel Beck commented on JENKINS-24458 Jenkins log file grows to 5GB in under 24 hours since last upgrade to 1.577 Which version did you have before upgrading to 1.576? Are you sure the exceptions did not occur on 1.576 but only started once you updated to 1.577? 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] [core] (JENKINS-21977) java.io.IOException: Failed to clean up temp dirs because of secret.key
Jesse Glick started work on JENKINS-21977 java.io.IOException: Failed to clean up temp dirs because of secret.key Change By: Jesse Glick (27/Aug/14 1:41 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
