[JIRA] [instant-messaging-plugin] (JENKINS-22042) IRCBot disconnects after long idle
Herman van Rink commented on JENKINS-22042 IRCBot disconnects after long idle Kutzi, I agree that it's not a proper solution. Some form of re-connect would probably be needed. What I had hoped the build-timeout plugin to solve is to stop a build that is hanging on the notification. A failed build would alert me of an issue, letting me restart Jenkins if needed to get the IRC connection back. The ironic thing is that the notification is an after-build step, that's why the build-timeout plugin did not help. Without a timeout it could be a week before anyone noticed that the builds have stalled. 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] [remoting] (JENKINS-24761) Jenkin job fails with hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown
David Rubio commented on JENKINS-24761 Jenkin job fails with hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown Same problem here. Master is Ubuntu 12.04 x64 with Jenkins 1.597. The slave is a Windows 7 machine. 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-26857) Out Of Memory Error
Robert Beddow created JENKINS-26857 Out Of Memory Error Issue Type: Bug Assignee: Unassigned Components: core Created: 09/Feb/15 9:12 AM Description: I am having trouble with Jenkins being killed by an out of memory process. After it is killed with the following info: Feb 6, 2015 12:54:07 PM hudson.model.AsyncPeriodicWork$1 run INFO: Finished Out of order build detection. 279,864 ms Feb 6, 2015 12:59:10 PM hudson.model.Run execute INFO: job_name #274 main build action completed: SUCCESS Killed I think there was some time (minutes or more) between the last INFO and Killed, so I don't think they're related. dmesg gives: Out of memory: Kill process 20715 (java) score 633 or sacrifice child Killed process 20715, UID 163, (java) total-vm:4779076kB, anon-rss:247kB, file-rss:260kB java invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=0, oom_score_adj=0 java cpuset=/ mems_allowed=0 I run Jenkins with this command: export JENKINS_HOME=/jenkins_home; cd /home/user java -jar -Xmx4g -XX:+HeapDumpOnOutOfMemoryError jenkins.war I'm running version: Jenkins ver. 1.595 I have a heap dump, but it was dumped hours before the job was killed, so I'm not sure of it's use I'm also running Java VisualVM, but I've never used this before, so I don't really know what to look for. I've been trying to follow: https://wiki.jenkins-ci.org/display/JENKINS/I%27m+getting+OutOfMemoryError But I'm a little lost. My heap dumps show a number of classes with well over 100,000 instances, e.g.: java.lang.String, char[], java.util.HashMap$Entry I don't know where to go from here. Does anyone have any suggestions? Environment: Jenkins ver. 1.595 Linux 2.6.32-358.23.2.el6.x86_64 #1 SMP Sat Sep 14 05:32:37 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux Chrome java version 1.6.0_24 OpenJDK Runtime Environment (IcedTea6 1.11.5) (rhel-1.50.1.11.5.el6_3-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) Project: Jenkins Priority: Critical Reporter: Robert Beddow 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-plugin] (JENKINS-18834) prune should be before fetch
packadal edited a comment on JENKINS-18834 prune should be before fetch This problematic behavior is still present in Jenkins 1.596 with git plugin version 2.3.4. I see a git fetch repo --prune which is not sufficient. There should be something along the lines of "git remote prune origin" BEFORE the fetch. 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-plugin] (JENKINS-18834) prune should be before fetch
packadal commented on JENKINS-18834 prune should be before fetch This problematic behavior is still present in Jenkins 1.596 with git plugin version 2.3.4. 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-plugin] (JENKINS-18834) prune should be before fetch
packadal reopened JENKINS-18834 prune should be before fetch Change By: packadal (09/Feb/15 9:30 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-12193) Hook up injected tests
SCM/JIRA link daemon commented on JENKINS-12193 Hook up injected tests Code changed in jenkins User: Daniel Spilker Path: CHANGELOG.md src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiExtension.groovy src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiPlugin.groovy src/main/groovy/org/jenkinsci/gradle/plugins/jpi/TestInsertionTask.groovy src/test/groovy/org/jenkinsci/gradle/plugins/jpi/JpiPluginSpec.groovy http://jenkins-ci.org/commit/gradle-jpi-plugin/fc956747d8ea5150984e0e86b811dd9113b77582 Log: JENKINS-12193 hook up injected tests, but disabled by default because of JENKINS-21977 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
SCM/JIRA link daemon commented on JENKINS-21977 java.io.IOException: Failed to clean up temp dirs because of secret.key Code changed in jenkins User: Daniel Spilker Path: CHANGELOG.md src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiExtension.groovy src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiPlugin.groovy src/main/groovy/org/jenkinsci/gradle/plugins/jpi/TestInsertionTask.groovy src/test/groovy/org/jenkinsci/gradle/plugins/jpi/JpiPluginSpec.groovy http://jenkins-ci.org/commit/gradle-jpi-plugin/fc956747d8ea5150984e0e86b811dd9113b77582 Log: JENKINS-12193 hook up injected tests, but disabled by default because of JENKINS-21977 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] [warnings-plugin] (JENKINS-18708) Make it possible to have several files as input for one parser
Csaba Gyorfi commented on JENKINS-18708 Make it possible to have several files as input for one parser I have the same issue. In my build project there are two GNU/C++ project and I want to see the results separated, in two graphs. But this is not working as described. As a workaround, it would be nice if I could clone the GNU/C++ parser with a new name, and than use this cloned parser for the second log file. Is there an easy way to clone the GNU/C++ parser without the need of the plugin dev environment? 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] [gradle-jpi-plugin] (JENKINS-12193) Hook up injected tests
SCM/JIRA link daemon commented on JENKINS-12193 Hook up injected tests Code changed in jenkins User: Daniel Spilker Path: CHANGELOG.md src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiExtension.groovy src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiPlugin.groovy src/main/groovy/org/jenkinsci/gradle/plugins/jpi/TestInsertionTask.groovy src/test/groovy/org/jenkinsci/gradle/plugins/jpi/JpiPluginSpec.groovy http://jenkins-ci.org/commit/gradle-jpi-plugin/0031ffab8800923fc38bdc123edc1742ee3438dc Log: Merge pull request #42 from daspilker/JENKINS-12193 JENKINS-12193 Hook up injected tests Compare: https://github.com/jenkinsci/gradle-jpi-plugin/compare/9f6de01dd6ad...0031ffab8800 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] [gradle-jpi-plugin] (JENKINS-12193) Hook up injected tests
Daniel Spilker resolved JENKINS-12193 as Fixed Hook up injected tests Will be released in 0.8.2. Change By: Daniel Spilker (09/Feb/15 9:49 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26861) Invoke top-level Maven targets pre-/post-step should use batch mode
Jakub Bochenski created JENKINS-26861 Invoke top-level Maven targets pre-/post-step should use batch mode Issue Type: Bug Assignee: Unassigned Components: core Created: 09/Feb/15 4:48 PM Description: Duh.. not enabling batch mode can result in build hanging waiting for input Project: Jenkins Priority: Major Reporter: Jakub Bochenski 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-26862) Jenkins should set a SecurityManager (prevent rogue scripts exiting)
Ed Randall created JENKINS-26862 Jenkins should set a SecurityManager (prevent rogue scripts exiting) Issue Type: Improvement Assignee: vjuranek Components: core, groovy-plugin Created: 09/Feb/15 5:02 PM Description: Jenkins should set a SecurityManager and explicity trap out calls to System.exit from plugins. This would prevent eg. the following script from taking out the whole web container: System.exit(0) Groovy even provides a NoExitSecurityManager for this purpose. Environment: Any Project: Jenkins Priority: Major Reporter: Ed Randall 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] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Cletus DSouza updated JENKINS-26770 version 1.29 of the plugin does not work! To assist with your predicament, I've created a one-off version that doesn't check for 'Configuration Name' uniqueness when a new job is created. This will eliminate the NPE you're getting when trying to save configuration/create new. Change By: Cletus DSouza (09/Feb/15 4:33 PM) Attachment: integrity-plugin.hpi 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] [groovy-plugin] (JENKINS-14023) System.exit (13) in a groovy script causes Jenkins shutdown
Ed Randall commented on JENKINS-14023 System.exit (13) in a groovy script causes Jenkins shutdown This behaviour could probably be fixed by setting a securitymanager. Groovy even provides NoExitSecurityManager for this exact purpose. See http://stackoverflow.com/questions/1429610/prevent-system-exit-in-a-groovy-web-console-without-security-policy-file 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] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Cletus DSouza edited a comment on JENKINS-26770 version 1.29 of the plugin does not work! To assist with your predicament, I've created a one-off integrity-plugin.hpi version that doesn't check for 'Configuration Name' uniqueness when a new job is created. This will eliminate the NPE you're getting when trying to save configuration/create new. 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] [xcode-plugin] (JENKINS-24874) Xcode plugin hangs when using xcode6
Raphael Couto edited a comment on JENKINS-24874 Xcode plugin hangs when using xcode6 lacostej, I've forked the project at github (https://github.com/raphaelquati/xcode-plugin), and tested your patch (you wrote in early comments). I've made little changes in the code. Now the build is working. I've created an pull request. 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-client-plugin] (JENKINS-26871) Test
parveen banu resolved JENKINS-26871 as Fixed Test Change By: parveen banu (10/Feb/15 5:31 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] [multijob-plugin] (JENKINS-23967) Parametrised Job that should not trigger triggered anyways
Michelle Sinotte commented on JENKINS-23967 Parametrised Job that should not trigger triggered anyways I'm having this same issue. My environment is (Jenkins ver 1.580.2=LTS, Multijob plugin=1.16, Parameterized Trigger plugin=2.25). FYI, the summary has Parameteris(z)ed misspelled. If it could be corrected, it might help with searches. 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-client-plugin] (JENKINS-26871) Test
parveen banu created JENKINS-26871 Test Issue Type: Bug Assignee: parveen banu Components: git-client-plugin Created: 10/Feb/15 5:27 AM Description: test Project: Jenkins Priority: Minor Reporter: parveen banu 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-plugin] (JENKINS-26872) Test
parveen banu assigned JENKINS-26872 to Nicolas De Loof Test Change By: parveen banu (10/Feb/15 5:42 AM) Assignee: parveenbanu NicolasDeLoof This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
Ximon Eighteen edited a comment on JENKINS-26854 EC2 slave launch stops working after a while with AmazonServiceException Request has expired I tried building the EC2 plugin with AWS Java SDK 1.8.11, the first stable release after 1.8.10 that introduced the new InstanceProfileCredentialsProvider(true) functionality. This solves the missing refetch of credentials, causing the SDK to check them once a minute. However, it fails with the Auth error I referred to above: com.amazonaws.AmazonServiceException: AWS was not able to validate the provided access credentials (Service: AmazonEC2; Status Code: 401; Error Code: AuthFailure; Request ID: 0ad2caa1-4f05-41e7-b168-3dc37940265b) at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1032) at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:687) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:441) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:292) at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:9225) at com.amazonaws.services.ec2.AmazonEC2Client.describeKeyPairs(AmazonEC2Client.java:6321) at com.amazonaws.services.ec2.AmazonEC2Client.describeKeyPairs(AmazonEC2Client.java:8879) at hudson.plugins.ec2.EC2PrivateKey.find(EC2PrivateKey.java:135) at hudson.plugins.ec2.SlaveTemplate.getKeyPair(SlaveTemplate.java:719) at hudson.plugins.ec2.SlaveTemplate.provisionOndemand(SlaveTemplate.java:303) at hudson.plugins.ec2.SlaveTemplate.provision(SlaveTemplate.java:287) at hudson.plugins.ec2.EC2Cloud.doProvision(EC2Cloud.java:283) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java: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:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.service(Stapler.java:237) 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.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] [remoting] (JENKINS-26855) Unreachable objects remoting.Channel can not garbage collect
denger tung commented on JENKINS-26855 Unreachable objects remoting.Channel can not garbage collect found many waring log in tomcat: 10, 2015 2:38:09 hudson.node_monitors.AbstractNodeMonitorDescriptor$Record init waring: Previous Architecture monitoring activity still in progress. Interrupting 10, 2015 2:38:09 hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor monitor waring: Failed to monitor oped-slave-08-argus-cp185 for Clock Difference hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:549) at hudson.remoting.Request.callAsync(Request.java:204) at hudson.remoting.Channel.callAsync(Channel.java:778) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:76) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:280) Caused by: java.nio.channels.AsynchronousCloseException at java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:205) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:412) at hudson.remoting.SocketChannelStream$1.read(SocketChannelStream.java:35) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:65) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:109) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103) at java.io.InputStream.read(InputStream.java:101) at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:81) at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2293) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2586) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2596) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1318) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:70) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) 10, 2015 2:38:09 hudson.node_monitors.AbstractNodeMonitorDescriptor$Record init waring: Previous Clock Difference monitoring activity still in progress. Interrupting 10, 2015 2:38:09 hudson.node_monitors.AbstractNodeMonitorDescriptor$Record init 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-26870) java.io.IOException on LogRotator
Astro Ashtar created JENKINS-26870 java.io.IOException on LogRotator Issue Type: Bug Assignee: Unassigned Attachments: jenkins.0.err.log Components: core Created: 10/Feb/15 2:41 AM Description: I run a lot of jobs and at some interval, I get the error below. I'm not 100% sure but I feel that when I get this error, jenkins goes into an unstable state. I get a HTTP Error 502.3 - Bad Gateway error when trying to access the site. The only way to bring Jenkins back online is to stop then restart the service. Feb 8, 2015 3:20:49 AM hudson.model.Run execute SEVERE: Failed to rotate log java.io.IOException: Run-a-Windows-Job #605397: C:\Program Files (x86)\Jenkins\jobs\Run-a-Windows-Job\builds\605397 looks to have already been deleted; siblings: [.605397, 2014-11-11_11-09-14, 2014-11-11_11-14-13, 2014-11-11_11-... (more here but i cut it down for this part, full error log is below) at hudson.model.Run.delete(Run.java:1462) at hudson.tasks.LogRotator.perform(LogRotator.java:129) at hudson.model.Job.logRotate(Job.java:465) at hudson.model.Run.execute(Run.java:1782) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) duplicate of error above but with full data. Feb 8, 2015 3:20:49 AM hudson.model.Run execute SEVERE: Failed to rotate log java.io.IOException: Run-a-Windows-Job #605397: C:\Program Files (x86)\Jenkins\jobs\Run-a-Windows-Job\builds\605397 looks to have already been deleted; siblings: .605397, 2014-11-11_11-09-14, 2014-11-11_11-14-13, 2014-11-11_11-19-54, 2014-11-11_11-19-58, 2014-11-11_11-20-00, 2014-11-11_11-20-01, 2014-11-11_11-20-02, 2014-11-11_11-20-03, 2014-11-11_11-20-04, 2014-11-12_10-21-31, 2014-11-12_10-21-42, 2014-11-12_10-21-48, 2014-11-12_10-26-17, 2014-11-12_10-27-49, 2014-11-12_10-28-41, 2014-11-12_10-28-44, 2014-11-12_10-28-53, 2014-11-12_10-28-54, 2014-11-12_10-28-56, 2014-11-12_10-28-57, 2014-11-12_10-28-58, 2014-11-12_10-46-06, 2014-11-12_10-46-12, 2014-11-12_10-46-21, 2014-11-12_10-49-40, 2014-11-12_10-50-19, 2014-11-12_10-53-25, 2014-11-12_12-45-48, 2014-11-12_12-46-45, 2014-11-12_12-46-54, 2014-11-12_12-47-04, 2014-11-12_12-47-23, 2014-11-12_23-45-22, 2014-11-12_23-57-51, 2014-11-12_23-57-52, 2014-11-13_23-58-04, 2014-11-19_22-30-01, 2014-11-20_00-00-01, 2014-12-03_04-31-46, 2014-12-03_04-34-10, 2014-12-03_04-38-01, 2014-12-03_04-38-06, 2014-12-03_13-28-37, 2014-12-03_13-28-51, 2014-12-03_13-28-52, 2014-12-03_13-29-58, 2014-12-03_13-30-03, 2014-12-05_23-58-04, 2014-12-16_23-59-18, 2014-12-21_23-58-04, 2015-01-01_23-58-04, 2015-01-02_23-58-04, 2015-01-05_23-58-03, 2015-01-30_23-48-14, 2015-01-30_23-48-16, 2015-01-30_23-54-56, 2015-01-30_23-56-04, 2015-01-30_23-56-31, 2015-01-30_23-57-29, 2015-01-30_23-57-46, 2015-01-30_23-57-50, 2015-01-30_23-57-56, 2015-01-30_23-57-58, 2015-01-30_23-58-08, 2015-01-30_23-58-29, 2015-01-30_23-58-58, 2015-01-30_23-59-01, 2015-02-03_17-29-18, 2015-02-04_11-58-02, 2015-02-04_12-00-08, 2015-02-04_12-00-09, 2015-02-04_12-03-57, 2015-02-04_12-03-58, 2015-02-04_12-03-59, 2015-02-04_12-04-00, 2015-02-04_12-04-02, 2015-02-04_12-04-03, 2015-02-04_12-04-04, 2015-02-04_12-04-05, 2015-02-04_12-04-06, 2015-02-04_12-04-08, 2015-02-04_12-04-09, 2015-02-04_12-04-10, 2015-02-04_12-04-11, 2015-02-04_12-04-12, 2015-02-04_12-04-14, 2015-02-04_12-04-53, 2015-02-04_12-05-09, 2015-02-04_12-05-19, 2015-02-04_12-05-33, 2015-02-04_12-05-39, 2015-02-04_12-05-42, 2015-02-04_12-06-12, 2015-02-04_12-06-18, 2015-02-04_12-06-21, 2015-02-04_12-06-22, 2015-02-04_12-06-30, 2015-02-04_12-06-42, 2015-02-04_12-06-43, 2015-02-04_12-06-44, 2015-02-04_12-06-45, 2015-02-04_12-06-46, 2015-02-04_12-06-47, 2015-02-04_12-06-48, 2015-02-04_12-06-49, 2015-02-04_12-06-50, 2015-02-04_12-06-51, 2015-02-04_12-06-52, 2015-02-04_12-06-57, 2015-02-04_12-07-02, 2015-02-04_12-07-15, 2015-02-04_12-07-51, 2015-02-04_12-07-54, 2015-02-04_12-07-57, 2015-02-04_12-08-02, 2015-02-04_12-08-10, 2015-02-04_12-08-15, 2015-02-04_12-08-16, 2015-02-04_12-08-18,
[JIRA] [slack-plugin] (JENKINS-26066) NPE for completed project without a slack configuration
SCM/JIRA link daemon commented on JENKINS-26066 NPE for completed project without a slack configuration Code changed in jenkins User: Sam Gleske Path: CHANGELOG.md README.markdown README.md pom.xml http://jenkins-ci.org/commit/slack-plugin/d6047ebe4344063178de1ef42304b69d453daf9c Log: Preparing for 1.7 release New features: Advanced settings Team domain and token can be specified per project; falls back to global config if not specified (#19) Post a list of commits with the build notification (title and author of commit) (#30, #44, #45) Include JUnit test summary in build notifications (#25) Use colors when sending a message using slack (#20, #24). Also, the start notifications use the color of the last build result (#43) Support for authenticated proxies (#14) Test Connection button (#46, #28) Option to disable subsequent notifications on build failures (#46, #15) Improvements: Report 'return to normal' on transition from unstable to success (#21) Improved logging. Bug fixes: When changing the global slack settings the slack config in jobs are updated as well (#26, #12) Fix NullPointerException and output log message if slack is not configured (#35, JENKINS-26066) 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] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
Ximon Eighteen commented on JENKINS-26854 EC2 slave launch stops working after a while with AmazonServiceException Request has expired I have created a minimal pull request. See: https://github.com/jenkinsci/ec2-plugin/pull/131 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] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Cletus DSouza commented on JENKINS-26770 version 1.29 of the plugin does not work! The stacktrace is a red-herring as it relates to the 'Apply' problem... Do you still have jobs that are running polling that don't seem to be reconfigured for the new plugin? If so, then that's what the stacktrace is about. You are correct in that the integrity-plugin is somehow causing the 'Apply' error. When I completely removed the plugin from my environment and re-configured the 'Test' job, I could click 'Apply' and it did work. Someone even the existence of the plugin, regardless of whether or not the job uses it causes the error. I don't know why as the logs are coming up empty. 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-plugin] (JENKINS-26872) Test
parveen banu created JENKINS-26872 Test Issue Type: Bug Assignee: parveen banu Components: git-plugin Created: 10/Feb/15 5:41 AM Project: Jenkins Priority: Minor Reporter: parveen banu 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-plugin] (JENKINS-26872) Test
parveen banu started work on JENKINS-26872 Test Change By: parveen banu (10/Feb/15 5:53 AM) 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.
[JIRA] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
Ximon Eighteen edited a comment on JENKINS-26854 EC2 slave launch stops working after a while with AmazonServiceException Request has expired I have no reason to think this is the cause of my problem but I just noticed that the plugin is built using v1.8.3 of the Java SDK while the latest version is 1.9.17, in theory at least there could be a bug fix in the newer versions. I looked through the release notes of the interim versions but didn't find an obvious bug fix that could be related to this issue. Update: Actually the release 1.8.10 of the Java SDK added the InstanceProfilerCredentialsProvider(true) behaviour I refer to above, but this was not directly mentioned in the release notes. This release was not a happy release, two hot fixes 1.8.10.1 and 1.8.10.2 were released in the following week. Update: If I build the EC2 plugin with the latest 1.9.17 SDK version it fails with an HTTP 401 Auth error which I haven't tracked down yet. I suspect this is because my AWS IAM InstanceProfile role does not include a permission which newer versions of the SDK require, but I haven't determined which permission is missing yet. 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] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
Ximon Eighteen commented on JENKINS-26854 EC2 slave launch stops working after a while with AmazonServiceException Request has expired I tried building the EC2 plugin with AWS Java SDK 1.8.11, the first stable release after 1.8.10 that introduced the new InstanceProfileCredentialsProvider(true) functionality. This solves the missing refetch of credentials, causing the SDK to check them once a minute. However, it fails with the Auth error I referred to above: com.amazonaws.AmazonServiceException: AWS was not able to validate the provided access credentials (Service: AmazonEC2; Status Code: 401; Error Code: AuthFailure; Request ID: 0ad2caa1-4f05-41e7-b168-3dc37940265b) at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1032) at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:687) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:441) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:292) at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:9225) at com.amazonaws.services.ec2.AmazonEC2Client.describeKeyPairs(AmazonEC2Client.java:6321) at com.amazonaws.services.ec2.AmazonEC2Client.describeKeyPairs(AmazonEC2Client.java:8879) at hudson.plugins.ec2.EC2PrivateKey.find(EC2PrivateKey.java:135) at hudson.plugins.ec2.SlaveTemplate.getKeyPair(SlaveTemplate.java:719) at hudson.plugins.ec2.SlaveTemplate.provisionOndemand(SlaveTemplate.java:303) at hudson.plugins.ec2.SlaveTemplate.provision(SlaveTemplate.java:287) at hudson.plugins.ec2.EC2Cloud.doProvision(EC2Cloud.java:283) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java: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:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.service(Stapler.java:237) 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.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] [gerrit-trigger-plugin] (JENKINS-26865) Matrix parent aborts when 'Exclude trivial rebase' set in gerrit-trigger plugin
rin_ne commented on JENKINS-26865 Matrix parent aborts when Exclude trivial rebase set in gerrit-trigger plugin This feature depends on Gerrit version. AFAIK 2.10 or later is needed. If earlier, this feature would be always disable. See patchset attribute in patchset-created event. 2.9.4 (no kind attribute) https://gerrit-documentation.storage.googleapis.com/Documentation/2.9.4/json.html#patchSet 2.10 (kind attribute has TRIVIAL_REBASE value) https://gerrit-documentation.storage.googleapis.com/Documentation/2.10/json.html#patchSet 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] [slack-plugin] (JENKINS-26066) NPE for completed project without a slack configuration
SCM/JIRA link daemon commented on JENKINS-26066 NPE for completed project without a slack configuration Code changed in jenkins User: Sam Gleske Path: CHANGELOG.md README.markdown README.md pom.xml http://jenkins-ci.org/commit/slack-plugin/178b34abfc6340abefbd7ee7ecc6b95295bc Log: Release Slack 1.7.0 New features: Advanced settings Team domain and token can be specified per project; falls back to global config if not specified (#19) Post a list of commits with the build notification (title and author of commit) (#30, #44, #45) Include JUnit test summary in build notifications (#25) Use colors when sending a message using slack (#20, #24). Also, the start notifications use the color of the last build result (#43) Support for authenticated proxies (#14) Test Connection button (#46, #28) Option to disable subsequent notifications on build failures (#46, #15) Improvements: Report 'return to normal' on transition from unstable to success (#21) Improved logging. Bug fixes: When changing the global slack settings the slack config in jobs are updated as well (#26, #12) Fix NullPointerException and output log message if slack is not configured (#35, JENKINS-26066) 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] [workflow-plugin] (JENKINS-26860) restrict parallel runs
Timur Batyrshin created JENKINS-26860 restrict parallel runs Issue Type: New Feature Assignee: Jesse Glick Components: workflow-plugin Created: 09/Feb/15 3:31 PM Description: It looks like the workflow-plugin job can't be restricted from being run several times in parallel. Project: Jenkins Priority: Major Reporter: Timur Batyrshin 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-26861) Invoke top-level Maven targets pre-/post-step should use batch mode
Daniel Beck commented on JENKINS-26861 Invoke top-level Maven targets pre-/post-step should use batch mode Is this specific to the Maven job type, or does this apply to all occurrences of the 'Invoke top-level maven targets' build step? 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] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Grigoriy Milman edited a comment on JENKINS-26770 version 1.29 of the plugin does not work! Usage of the integrity-plugin.hpi helps, but there is still a strange issue. There are two buttons on the config editing screen, "Save" and "Apply". Now by using "Save", config is saved and build job is executed OK (finally!). By using button "Apply" - grey empty screen appeared with "Error"on it (see attached picture ^ptc.jpg .). I have tried to "Save" and then "Apply" - "Apply" button does not work, always error screen, but "Save" works. It looks like it is last issue that need to be resolved here. 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] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Grigoriy Milman updated JENKINS-26770 version 1.29 of the plugin does not work! Change By: Grigoriy Milman (09/Feb/15 8:04 PM) Attachment: ConfigHistory.JPG 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] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Grigoriy Milman edited a comment on JENKINS-26770 version 1.29 of the plugin does not work! But the config has been already saved by "Save" button just a second before! It very simple: open config, save by "Save" button, than open config again and click "Apply" - error screen appeared. By the way, I have tried to see job config history by clicking "config changed since last build" at "Build history" (see ConfigHistory.JPG) and the following error appeared: HTTP ERROR 404 Problem accessing /view/BurnIn/job/NGMP.BurnIn.BoardScanner/jobConfigHistory/showDiffFiles. Reason: Not Found Powered by Jetty:// 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] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Grigoriy Milman commented on JENKINS-26770 version 1.29 of the plugin does not work! But the config has been already saved by "Save" button just a second before! It very simple: open config, save by "Save" button, than open config again and click "Apply" - error screen appeared. By the way, I have tried to see job config history by clicking "config changed since last build" at "Build history" (see) HTTP ERROR 404 Problem accessing /view/BurnIn/job/NGMP.BurnIn.BoardScanner/jobConfigHistory/showDiffFiles. Reason: Not Found Powered by Jetty:// 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] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Grigoriy Milman updated JENKINS-26770 version 1.29 of the plugin does not work! Change By: Grigoriy Milman (09/Feb/15 8:08 PM) Attachment: NewConfigHistory.JPG 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-trigger-plugin] (JENKINS-26865) Matrix parent aborts when 'Exclude trivial rebase' set in gerrit-trigger plugin
Eugene Korekin created JENKINS-26865 Matrix parent aborts when Exclude trivial rebase set in gerrit-trigger plugin Issue Type: Bug Assignee: rsandell Components: gerrit-trigger-plugin, matrix-project-plugin Created: 09/Feb/15 8:10 PM Description: I have multi-configuration job with two configurations. It triggered by gerrit trigger with option 'Exclude Trivial Rebase' When job is triggered by rebased patchset parent job is aborted and there is messages in log: review.vsphere » CentOS,vsphere appears to be cancelled review.vsphere » CentOS,vsphere completed with result ABORTED review.vsphere » Ubuntu,vsphere appears to be cancelled review.vsphere » Ubuntu,vsphere completed with result ABORTED Collecting metadata... Metadata collection done. Finished: ABORTED So it seems that gerrit trigger plugin prevents child jobs from running, matrix parent cannot find them, aborts and sets negative vote on patchset. In this case matrix parent should be cancelled too and vote should be skipped. Environment: Jenkins ver. 1.598 Matrix project plugin ver. 1.4 Gerrit trigger ver. 2.12.0 Project: Jenkins Priority: Minor Reporter: Eugene Korekin 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] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Grigoriy Milman commented on JENKINS-26770 version 1.29 of the plugin does not work! Usage of the integrity-plugin.hpi helps, but there is still a strange issue. There are two buttons on the config editing screen, "Save" and "Apply". Now by using "Save", config is saved and build job is executed OK (finally!). By using button "Apply" - grey empty screen appeared with "Error"on it (see attached picture). I have tried to "Save" and then "Apply" - "Apply" button does not work, always error screen, but "Save" works. It looks like it is last issue that need to be resolved here. 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] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Grigoriy Milman edited a comment on JENKINS-26770 version 1.29 of the plugin does not work! Usage of the integrity-plugin.hpi helps, but there is still a strange issue. There are two buttons on the config editing screen, "Save" and "Apply". Now by using "Save", config is saved and build job is executed OK (finally!). By using button "Apply" - grey empty screen appeared with "Error" on it (see attached picture ptc.JPG .). I have tried to "Save" and then "Apply" - "Apply" button does not work, always error screen, but "Save" works. It looks like it is last issue that need to be resolved here. 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] [ec2-plugin] (JENKINS-23705) EC2 slave disconnects on longer running builds
Jonathan Langevin commented on JENKINS-23705 EC2 slave disconnects on longer running builds Helpful resources for debugging this issue further: https://wiki.jenkins-ci.org/display/JENKINS/Ping+Thread https://wiki.jenkins-ci.org/display/JENKINS/Remoting+issue I've edited my JAVA args for Jenkins to add: -Dhudson.slaves.ChannelPinger.pingInterval=-1 Which should disable ping timeout on the master instance side. I'm running more builds to see if this helps the situation. 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] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Grigoriy Milman edited a comment on JENKINS-26770 version 1.29 of the plugin does not work! But the config has been already saved by "Save" button just a second before! It very simple: open config, save by "Save" button, than open config again and click "Apply" - error screen appeared. By the way, I have tried to see job config history by clicking "config changed since last build" at "Build history" (see ConfigHistory.JPG) HTTP ERROR 404 Problem accessing /view/BurnIn/job/NGMP.BurnIn.BoardScanner/jobConfigHistory/showDiffFiles. Reason: Not Found Powered by Jetty:// 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-trigger-plugin] (JENKINS-26865) Matrix parent aborts when 'Exclude trivial rebase' set in gerrit-trigger plugin
Eugene Korekin updated JENKINS-26865 Matrix parent aborts when Exclude trivial rebase set in gerrit-trigger plugin Change By: Eugene Korekin (09/Feb/15 8:10 PM) Priority: Minor Major 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] [integrity-plugin] (JENKINS-26016) PTC Plugin: Request to add postbuild action to label a project
Paul Sharpe commented on JENKINS-26016 PTC Plugin: Request to add postbuild action to label a project As I said before, I do not want to create a new checkpoint, but apply a label to an existing one (the one created before the build started). I think this would be a new action performing a "si addprojectlabel". But I guess I could simply create a job that invokes this command in the client... 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-26739) Executors are dying since 1.597 - related to the directory layout change?
Thomas Müller commented on JENKINS-26739 Executors are dying since 1.597 - related to the directory layout change? The job in question is based on the github pull request builder - might that be the reason? Could a quite period help? Let me try that ... 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] [test1] (TEST-45) builddddddddd
mohsin sheikh created TEST-45 build Issue Type: Patch Assignee: Kohsuke Kawaguchi Components: test1 Created: 09/Feb/15 8:23 AM Project: test Priority: Minor Reporter: mohsin sheikh 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] [remoting] (JENKINS-26855) Unreachable objects remoting.Channel can not garbage collect
denger tung updated JENKINS-26855 Unreachable objects remoting.Channel can not garbage collect a Channel 1MB Change By: denger tung (09/Feb/15 8:21 AM) Attachment: channel-listobjects.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] [integrity-plugin] (JENKINS-26856) Internal Server Error with integrity-plugin version 1.30
Florian Peschka created JENKINS-26856 Internal Server Error with integrity-plugin version 1.30 Issue Type: Bug Assignee: Cletus DSouza Components: integrity-plugin Created: 09/Feb/15 8:31 AM Description: When using integrity-plugin 1.30 and trying to configue the server connection, the log shows Feb 09, 2015 9:16:05 AM hudson.scm.APISession create SEVERE: Unexpected HTTP status: Internal Server Error Without further information about what exactly happened. It works fine with integrity-plugin 1.28 Environment: Jenkins 1.596 MKS Integrity 2007 SP 007-01 on Windows Server 2003 SP 1 Project: Jenkins Labels: integrity-plugin Priority: Major Reporter: Florian Peschka 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] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Grigoriy Milman commented on JENKINS-26770 version 1.29 of the plugin does not work! I have tried to migrate from 1.28 to 1.30 by doing the following: Turning off Integrity CM usage in the build jobs configurations, than saving build job configuration; Performing upgrade to the 1.30 plugin. Restarting Jenkins. Setting required PTC settings in Jenkins system configuration (old ones did disappear); For each build job configuration turning on Integrity CM usage, setting PTC project. Save configuration - null pointer exception happened! Good thing is that I have tried this experiment on the clone of the virtual system where Jenkins is running, so our production Jenkins server is still fine. Bad thin is that I still don't know how to migrate to new plugin from 1.28 with saving build history! What is more, creation of the new build job based on the old one does not work either! Any idea? 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-plugin] (JENKINS-26872) Test
Daniel Beck closed JENKINS-26872 as Not A Defect Test Idiot. Change By: Daniel Beck (10/Feb/15 7:52 AM) Status: InProgress Closed Assignee: NicolasDeLoof 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] [subversion-plugin] (JENKINS-26866) jenkins java.io.ioexception remote file operation failed
Daniel Beck commented on JENKINS-26866 jenkins java.io.ioexception remote file operation failed Please note: I am on holiday and have no access to this server other than by an e-mail chain with a colleague. Please forgive me if this takes some back and forth to get the necessary info. Please note that this is an issue tracker, and not a support site. So it doesn't matter if it takes a few weeks for you to provide additional information. 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-26869) /safeRestart or /restart command causes exception
Daniel Beck resolved JENKINS-26869 as Duplicate /safeRestart or /restart command causes exception Change By: Daniel Beck (10/Feb/15 7:40 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
Ximon Eighteen commented on JENKINS-26854 EC2 slave launch stops working after a while with AmazonServiceException Request has expired Ah, the AuthFailure may affect others too. See: https://forums.aws.amazon.com/thread.jspa?messageID=574914tstart=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] [walldisplay-plugin] (JENKINS-26873) Sorting by Status does not work correctly
Sven Finsterwalder updated JENKINS-26873 Sorting by Status does not work correctly Change By: Sven Finsterwalder (10/Feb/15 7:38 AM) Attachment: jenkins_job_list_sorted_by_status.png Attachment: walldisplay_config.png Attachment: walldisplay_dark.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] [core] (JENKINS-26866) jenkins java.io.ioexception remote file operation failed
Smouch Smouch edited a comment on JENKINS-26866 jenkins java.io.ioexception remote file operation failed Please note: I am on holiday and have no access to this server other than by an e-mail chain with a colleague. Please forgive me if this takes some back and forth to get the necessary info. Jenkins master configuration # awt.toolkit sun.awt.X11.XToolkit com.sun.akuma.Daemon daemonized executable-war /usr/lib/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / hudson.diyChunking true java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/lib/jenkins/jenkins.war java.class.version 51.0 java.endorsed.dirs /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/endorsed java.ext.dirs /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.7.0_75-mockbuild_2015_01_21_08_43-b00 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.7 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.7.0_75 java.vm.info mixed mode java.vm.name OpenJDK 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.7 java.vm.vendor Oracle Corporation java.vm.version 24.75-b04 JENKINS_HOME /var/lib/jenkins jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib jnidispatch.path /tmp/jna--1712433994/jna2593038690531263893.tmp line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 3.18.5-101.fc20.x86_64 path.separator : sun.arch.data.model 64 sun.boot.class.path /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/resources.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/rt.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/jsse.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/jce.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/charsets.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/rhino.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/jfr.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/classes sun.boot.library.path /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/amd64 sun.cpu.endian little sun.cpu.isalist sun.font.fontmanager sun.awt.X11FontManager sun.io.unicode.encoding UnicodeLittle sun.java.command /usr/lib/jenkins/jenkins.war --logfile=/var/log/jenkins/jenkins.log --webroot=/var/cache/jenkins/war --daemon --httpPort=8080 --ajp13Port=8009 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 sun.java.launcher SUN_STANDARD sun.jnu.encoding UTF-8 sun.management.compiler HotSpot 64-Bit Tiered Compilers sun.os.patch.level unknown svnkit.http.methods Digest,Basic,NTLM,Negotiate svnkit.ssh2.persistent false user.country US user.dir / user.home /var/lib/jenkins user.language en user.name jenkins user.timezone Europe/Berlin Environment Variables Name ↓ Value HOME /var/lib/jenkins LANG en_US.UTF-8 LOGNAME jenkins NLSPATH /usr/dt/lib/nls/msg/%L/%N.cat PATH /sbin:/usr/sbin:/bin:/usr/bin PWD / SHELL /bin/bash SHLVL 2 USER jenkins XFILESEARCHPATH /usr/dt/app-defaults/%L/Dt Plugins Name ↓ Version Enabled Pinned ant 1.2 false false antisamy-markup-formatter 1.1 false false build-monitor-plugin 1.6+build.138 true false credentials 1.18 true false cvs 2.11 false false email-ext 2.39 true false external-monitor-job 1.4 false false hudson-wsclean-plugin 1.0.4 true false javadoc 1.1 false false jenkinswalldisplay 0.6.27 true false junit 1.2-beta-4 true false ldap 1.8 false true mailer 1.15 true true matrix-auth 1.1 true false matrix-project 1.3 true false maven-plugin 2.7.1 false false multi-slave-config-plugin 1.0.0 true false pam-auth 1.1 false false
[JIRA] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
Ximon Eighteen edited a comment on JENKINS-26854 EC2 slave launch stops working after a while with AmazonServiceException Request has expired Ah, the AuthFailure may affect others too. See: https://forums.aws.amazon.com/thread.jspa?messageID=574914tstart=0. I'm seeing this issue in the eu-west-1 region. Update: Applying the force previous signer configuration solved this issue for me, that is this part of the forum article that I referred to: clientConfiguration.setSignerOverride(“QueryStringSignerType”); AmazonEC2 ec2 = new AmazonEC2Client(configuration); 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-26528) build.delete() should throw if build is marked as keep forever
Daniel Beck resolved JENKINS-26528 as Wont Fix build.delete() should throw if build is marked as keep forever JENKINS-26281 has been merged a while back, allowing users to delete builds even if marked to be kept. This would break that other behavior. Change By: Daniel Beck (10/Feb/15 7:57 AM) Status: Open Resolved Resolution: WontFix 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] [walldisplay-plugin] (JENKINS-26873) Sorting by Status does not work correctly
Sven Finsterwalder created JENKINS-26873 Sorting by Status does not work correctly Issue Type: Bug Assignee: Christian Pelster Components: walldisplay-plugin Created: 10/Feb/15 7:34 AM Description: I have set the sort Order to "Job status", but when i open a wall display view is seems to be random order and not by job status. Project: Jenkins Priority: Minor Reporter: Sven Finsterwalder 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-26866) jenkins java.io.ioexception remote file operation failed
Smouch Smouch reopened JENKINS-26866 jenkins java.io.ioexception remote file operation failed Jenkins master configuration # awt.toolkit sun.awt.X11.XToolkit com.sun.akuma.Daemon daemonized executable-war /usr/lib/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / hudson.diyChunking true java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/lib/jenkins/jenkins.war java.class.version 51.0 java.endorsed.dirs /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/endorsed java.ext.dirs /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.7.0_75-mockbuild_2015_01_21_08_43-b00 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.7 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.7.0_75 java.vm.info mixed mode java.vm.name OpenJDK 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.7 java.vm.vendor Oracle Corporation java.vm.version 24.75-b04 JENKINS_HOME /var/lib/jenkins jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib jnidispatch.path /tmp/jna--1712433994/jna2593038690531263893.tmp line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 3.18.5-101.fc20.x86_64 path.separator : sun.arch.data.model 64 sun.boot.class.path /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/resources.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/rt.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/jsse.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/jce.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/charsets.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/rhino.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/jfr.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/classes sun.boot.library.path /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.75-2.5.4.2.fc20.x86_64/jre/lib/amd64 sun.cpu.endian little sun.cpu.isalist sun.font.fontmanager sun.awt.X11FontManager sun.io.unicode.encoding UnicodeLittle sun.java.command /usr/lib/jenkins/jenkins.war --logfile=/var/log/jenkins/jenkins.log --webroot=/var/cache/jenkins/war --daemon --httpPort=8080 --ajp13Port=8009 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 sun.java.launcher SUN_STANDARD sun.jnu.encoding UTF-8 sun.management.compiler HotSpot 64-Bit Tiered Compilers sun.os.patch.level unknown svnkit.http.methods Digest,Basic,NTLM,Negotiate svnkit.ssh2.persistent false user.country US user.dir / user.home /var/lib/jenkins user.language en user.name jenkins user.timezone Europe/Berlin Environment Variables Name ↓ Value HOME /var/lib/jenkins LANG en_US.UTF-8 LOGNAME jenkins NLSPATH /usr/dt/lib/nls/msg/%L/%N.cat PATH /sbin:/usr/sbin:/bin:/usr/bin PWD / SHELL /bin/bash SHLVL 2 USER jenkins XFILESEARCHPATH /usr/dt/app-defaults/%L/Dt Plugins Name ↓ Version Enabled Pinned ant 1.2 false false antisamy-markup-formatter 1.1 false false build-monitor-plugin 1.6+build.138 true false credentials 1.18 true false cvs 2.11 false false email-ext 2.39 true false external-monitor-job 1.4 false false hudson-wsclean-plugin 1.0.4 true false javadoc 1.1 false false jenkinswalldisplay 0.6.27 true false junit 1.2-beta-4 true false ldap 1.8 false true mailer 1.15 true true matrix-auth 1.1 true false matrix-project 1.3 true false maven-plugin 2.7.1 false false multi-slave-config-plugin 1.0.0 true false pam-auth 1.1 false false parameterized-trigger 2.25 true false scm-api 0.2 true false script-security 1.10 true false ssh-credentials 1.10 true false ssh-slaves 1.9 false false subversion 2.2 true true token-macro 1.10 true
[JIRA] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
Ximon Eighteen edited a comment on JENKINS-26854 EC2 slave launch stops working after a while with AmazonServiceException Request has expired Ah, the AuthFailure may affect others too. See: https://forums.aws.amazon.com/thread.jspa?messageID=574914tstart=0. I'm seeing this issue in the eu-west-1 region. 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-plugin] (JENKINS-26866) jenkins java.io.ioexception remote file operation failed
Daniel Beck updated JENKINS-26866 jenkins java.io.ioexception remote file operation failed Still no mention of Jenkins version. Since there are two release lines (LTS and weekly), "current" is unhelpful. I've seen this (or a similar) issue before, it's probably due to the design of Subversion Plugin that causes Jenkins to try to transfer unremotable classes to be transferred via the remoting channel. The log (either master's jenkins.log or the slave's log) should contain another related error. Change By: Daniel Beck (10/Feb/15 7:48 AM) Component/s: subversion-plugin Component/s: core 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] [url-auth] (JENKINS-26863) Subdirectories/subfolders in svn repository not accessible through url on jenkins
Soe Naing updated JENKINS-26863 Subdirectories/subfolders in svn repository not accessible through url on jenkins Change By: Soe Naing (09/Feb/15 5:26 PM) Component/s: swarm-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [artifact-diff-plugin] (JENKINS-26628) How to get version of files and import them in a job
Daniel Beck resolved JENKINS-26628 as Not A Defect How to get version of files and import them in a job This is an issue tracker, not a support site. Change By: Daniel Beck (09/Feb/15 5:51 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [port-allocator-plugin] (JENKINS-26864) allow in port allocator Pool definitions to define a range
Vitaly Bichov created JENKINS-26864 allow in port allocator Pool definitions to define a range Issue Type: New Feature Assignee: ramapulavarthi Components: port-allocator-plugin Created: 09/Feb/15 6:25 PM Description: Pool definitions should be able to receive a range of ports and not only comma delimited list. I.E: 1024-2048 Those inputs could be mixed: I.E: 1088,2000-3000,4999 Project: Jenkins Priority: Minor Reporter: Vitaly Bichov 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] [ec2-plugin] (JENKINS-23705) EC2 slave disconnects on longer running builds
Jonathan Langevin commented on JENKINS-23705 EC2 slave disconnects on longer running builds Slave disconnects had seemed to reduce occurrence for me for awhile there, but I'm now again experiencing intermittent disconnects. I connected to the slave directly, and found slave.jar was still running. It seems this causes an issue, because if I tell the Master to reconnect to the Slave, it launched a second slave.jar instance on the slave, rather than reconnecting to the already running instance. And then, of course, the job(s) that were running, never get their status updated. It seems to me that Ping is simply unreliable, as it's what's killing the instance connections, it would appear. Log: https://gist.github.com/intel352/0fd5ff26205a3e456c39 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] [swarm-plugin] (JENKINS-26863) Subdirectories/subfolders in svn repository not accessible through url on jenkins
Soe Naing created JENKINS-26863 Subdirectories/subfolders in svn repository not accessible through url on jenkins Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: jenkins problem.png Components: swarm-plugin, url-auth Created: 09/Feb/15 5:22 PM Description: Jenkins will not recognize the subfolders in svn repository (See attached image). It recognizes the svn url without the subfolders, however. It might be because the subversion version got upgraded and the current jenkins version does not allot for that change. Environment: Jenkins version- 1.498, OS- windows, Web browser- chrome, firefox (latest versions) Project: Jenkins Labels: subversion jenkins build Priority: Minor Reporter: Soe Naing 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-26780) Auto-installer for JDK no longer works
Daniel Beck commented on JENKINS-26780 Auto-installer for JDK no longer works Do you log requests to Jenkins? It seems it used the regular update center JSON for JDK installers. Would be interesting to see how this happened. 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-26862) Jenkins should set a SecurityManager (prevent rogue scripts exiting)
Daniel Beck commented on JENKINS-26862 Jenkins should set a SecurityManager (prevent rogue scripts exiting) Wouldn't it suffice to fix plugins so they use Script Security Plugin for everything groovy? 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] [url-auth] (JENKINS-26863) Subdirectories/subfolders in svn repository not accessible through url on jenkins
Daniel Beck resolved JENKINS-26863 as Cannot Reproduce Subdirectories/subfolders in svn repository not accessible through url on jenkins Needs to happen with current Jenkins and Subversion Plugin versions. 1.498 is two years obsolete. Much more information is needed to investigate further, see https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue Change By: Daniel Beck (09/Feb/15 6:16 PM) Status: Open Resolved Resolution: CannotReproduce 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] [url-auth] (JENKINS-26863) Subdirectories/subfolders in svn repository not accessible through url on jenkins
Daniel Beck commented on JENKINS-26863 Subdirectories/subfolders in svn repository not accessible through url on jenkins http://zldv3697.vci.att.com:8080/jenkins/ Intranet-only URL, so irrelevant for a public issue tracker. 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-plugin] (JENKINS-26842) Branch Specifier regex fails - passed to git rev-parse?
Mark Waite resolved JENKINS-26842 as Fixed Branch Specifier regex fails - passed to git rev-parse? To be included in git plugin 2.3.5 Change By: Mark Waite (10/Feb/15 12:25 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-26855) Unreachable objects remoting.Channel can not garbage collect
denger tung commented on JENKINS-26855 Unreachable objects remoting.Channel can not garbage collect 2015-02-10T01:57:25.841+0800: 94114.387: CMS-concurrent-sweep-start 2015-02-10T01:57:26.905+0800: 94115.451: CMS-concurrent-sweep: 1.030/1.064 secs Times: user=1.54 sys=0.15, real=1.06 secs 2015-02-10T01:57:26.905+0800: 94115.451: CMS-concurrent-reset-start 2015-02-10T01:57:27.007+0800: 94115.553: CMS-concurrent-reset: 0.094/0.102 secs Times: user=0.18 sys=0.02, real=0.10 secs 2015-02-10T01:57:29.010+0800: 94117.556: [GC 1 CMS-initial-mark: 34116805K(37748736K) 35337096K(41523648K), 0.2135940 secs] Times: user=0.22 sys=0.00, real=0.21 secs 2015-02-10T01:57:29.224+0800: 94117.770: CMS-concurrent-mark-start 2015-02-10T01:57:30.770+0800: 94119.316: CMS-concurrent-mark: 1.481/1.546 secs Times: user=6.56 sys=0.34, real=1.54 secs 2015-02-10T01:57:30.770+0800: 94119.316: CMS-concurrent-preclean-start 2015-02-10T01:57:30.855+0800: 94119.401: CMS-concurrent-preclean: 0.085/0.085 secs Times: user=0.09 sys=0.00, real=0.09 secs 2015-02-10T01:57:30.856+0800: 94119.401: CMS-concurrent-abortable-preclean-start CMS: abort preclean due to time 2015-02-10T01:57:35.990+0800: 94124.535: CMS-concurrent-abortable-preclean: 3.800/5.134 secs Times: user=3.86 sys=0.00, real=5.13 secs 2015-02-10T01:57:35.993+0800: 94124.538: [GCYG occupancy: 1955888 K (3774912 K)2015-02-10T01:57:35.993+0800: 94124.538: Rescan (parallel) , 0.6148460 secs2015-02-10T01:57:36.608+0800: 94125.153: weak refs processing, 0.520 secs2015-02-10T01:57:36.608+0800: 94125.153: scrub string table, 0.0026450 secs 1 CMS-remark: 34116805K(37748736K) 36072693K(41523648K), 0.6178070 secs] Times: user=6.03 sys=0.00, real=0.61 secs 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-15) New post-build action: trigger other builds
SCM/JIRA link daemon commented on JENKINS-15 New post-build action: trigger other builds Code changed in jenkins User: Phil Path: pom.xml src/main/java/jenkins/plugins/slack/ActiveNotifier.java src/main/java/jenkins/plugins/slack/SlackNotifier.java src/main/java/jenkins/plugins/slack/StandardSlackService.java src/main/resources/jenkins/plugins/slack/SlackNotifier/SlackJobProperty/config.jelly src/main/resources/jenkins/plugins/slack/SlackNotifier/global.jelly src/main/webapp/help-projectConfig-testConnection.html http://jenkins-ci.org/commit/slack-plugin/8ab6a13cc53eb3035698f84c1316ac2e720acee0 Log: JENKINS-15JENKINS-28 Added option to notify repeated failure Option is set to true by default. Also added two test connection buttons in global and build slack settings. 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-28) drop-down menu for CVSROOT
SCM/JIRA link daemon commented on JENKINS-28 drop-down menu for CVSROOT Code changed in jenkins User: Phil Path: pom.xml src/main/java/jenkins/plugins/slack/ActiveNotifier.java src/main/java/jenkins/plugins/slack/SlackNotifier.java src/main/java/jenkins/plugins/slack/StandardSlackService.java src/main/resources/jenkins/plugins/slack/SlackNotifier/SlackJobProperty/config.jelly src/main/resources/jenkins/plugins/slack/SlackNotifier/global.jelly src/main/webapp/help-projectConfig-testConnection.html http://jenkins-ci.org/commit/slack-plugin/8ab6a13cc53eb3035698f84c1316ac2e720acee0 Log: JENKINS-15JENKINS-28 Added option to notify repeated failure Option is set to true by default. Also added two test connection buttons in global and build slack settings. 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] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
Ximon Eighteen edited a comment on JENKINS-26854 EC2 slave launch stops working after a while with AmazonServiceException Request has expired I'm going to put some logging into a subclass of InstanceProfilerCredentialsProvider() because I suspect that for some reason the credentials are not being refreshed by this class... will let you know what I find out. Update: Indeed the EC2 credential refresh functionality of the AWS Java SDK is not invoked. See attached jenkins.log (look for lines containing "Ximon:") and gitdiff.txt. Rough highlights from the log (might not be entirely accurate, trying to remember what I did last night): 11:33:00 UTC: Jenkins finished responding to a /safeRestart request that I performed. 11:34:36 UTC: I instructed Jenkins to launch a new EC2 slave. The EC2 plugin fetched the EC2 credentials as part of launching the instance. 11:45:46 UTC: I instructed Jenkins to terminate the EC2 slave. The EC2 plugin did not refetch the credentials. 11:46:09 UTC: I instructed Jenkins to launch a new EC2 slave. The EC2 plugin did not refetch the credentials. 12:22:46 UTC: The EC2 plugin correctly stopped the EC2 slave instance after the idle timeout expired. The EC2 plugin did not refetch the credentials. 04:32:58 UTC: UNRELATED BUG: Jenkins logged "Making NODE NAME (i-a2a41545) offline because it’s not responding". Why is this logged over 4 hours after the EC2 plugin stopped the slave? 05:30:22 UTC: I refreshed the Jenkins log web page which seems to have caused the EC2 plugin to attempt to update its knowledge about the state of the slave. By this point the EC2 credentials have expired, but the EC2 plugin did not refetch the credentials. The call to the EC2 API failed with HTTP 400 AmazonServiceException "Request has expired". 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-plugin] (JENKINS-25129) SCM Sync Shows Errors in the logs but GIT show no issues.
C. Alex Reober updated JENKINS-25129 SCM Sync Shows Errors in the logs but GIT show no issues. Change By: C. Alex Reober (09/Feb/15 8:27 PM) Priority: Minor Major 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] [promoted-builds-plugin] (JENKINS-3549) Display promotion stars on dashboard and main build history
AnneTheAgile commented on JENKINS-3549 Display promotion stars on dashboard and main build history There is an open PR; https://github.com/jenkinsci/promoted-builds-plugin/pull/30 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-26866) jenkins java.io.ioexception remote file operation failed
Smouch Smouch created JENKINS-26866 jenkins java.io.ioexception remote file operation failed Issue Type: Bug Assignee: Unassigned Components: core Created: 09/Feb/15 8:52 PM Description: Jenkins jobs assigned to java web-start slaves. The jobs in question were all working fine. Suddenly I get: jenkins java.io.ioexception remote file operation failed The call stack is essentially useless, and points to an exception handler in some Java class without indicating what exactly was attempted. Unfortunately this occurred just as I was preparing for a holiday. I do not have exact call stack now (I'm on a train). I fixed the problem by making the script explicitly perform a svn checkout/update rather than the normal method where one provides the URL and credentials in the fields for the "configure" page. That should be a good indication of where the issue lies. I really would like some kind of feedback on this issue, even though I will be away for a week. I would like to have the "normal" functionality and am willing to help investigate. Environment is: Fedora 21 x86_64 - all updates current as of 09.Feb.2015 Master and slaves are identical. I appreciate any help. Environment: Jenkins version is whatever the latest version is as of 09.FEB.2015 Project: Jenkins Labels: exception slave subversion Priority: Critical Reporter: Smouch Smouch 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] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method #39;next#39; in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendNoLevelsIgnoreGroup(MailingListCompiler.java:413)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendToAll(MailingListCompiler.java:408)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:140)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
style
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
/style
div id=email-body
table id=email-wrap align=center border=0 cellpadding=0
cellspacing=0 style=background-color:#f0f0f0;color:#00;width:100%;
tr valign=top
td id=email-page style=padding:16px !important;
table align=center border=0 cellpadding=0 cellspacing=0
style=background-color:#ff;border:1px solid
#bb;color:#00;width:100%;
tr valign=top
td bgcolor=#33
style=background-color:#33;color:#ff;font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:12px;line-height:1;img
src=https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png;
alt= style=vertical-align:top; //td
/trtr valign=top
td id=email-banner style=padding:32px 32px 0 32px;
table align=left border=0 cellpadding=0 cellspacing=0
width=100% style=width:100%;
tr valign=top
td
style=color:#505050;font-family:Arial,FreeSans,Helvetica,sans-serif;padding:0;
img id=email-avatar
src=https://issues.jenkins-ci.org/secure/useravatar?ownerId=rtyleravatarId=10787;
alt= height=48 width=48 border=0 align=left style=padding:0;margin:
0 16px 16px 0; /
div id=email-action style=padding: 0 0 8px
0;font-size:12px;line-height:18px;
a class=user-hover rel=rtyler
id=email_rtyler
href=https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=rtyler;
style=color:#355564;R. Tyler Croy/a
deleted img
src=https://issues.jenkins-ci.org/images/icons/genericissue.gif; height=16
width=16 border=0 align=absmiddle alt=Patch TEST-45
[JIRA] [scm-sync-configuration-plugin] (JENKINS-25129) SCM Sync Shows Errors in the logs but GIT show no issues.
C. Alex Reober commented on JENKINS-25129 SCM Sync Shows Errors in the logs but GIT show no issues. This is becoming a major issue: updated the system: Jenkins ver. 1.598 Now the message is: [DATE-TIME] Error while copying file hierarchy to SCM checkouted directory 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] [promoted-builds-plugin] (JENKINS-10068) Ability to remove a Promotion on a promoted build
AnneTheAgile commented on JENKINS-10068 Ability to remove a Promotion on a promoted build I am a newbie but I would consider writing a PR for this if I had some pointers. Before doing so, I think we should clarify scope. I think we could do this in parts. Part-1: Remove the star icon, just revert to regular. - I should certainly be able to help implement that. Part-2: Undo particular actions. This seems much more complex and would require matching items for each promotion action? Perhaps a simpler way would be: provide new custom actions, copying all the choices from the 'promote' into the 'demote' section of codes. Do we agree on this? Anne ps the freedom sponsors url gives 404. I'm curious to see one of those sometime! 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-26866) jenkins java.io.ioexception remote file operation failed
Daniel Beck resolved JENKINS-26866 as Incomplete jenkins java.io.ioexception remote file operation failed Report needs much more information, such as the exact error message and stack trace. Relevant jenkins.log excerpts would be useful as well. And "version is whatever is latest as of (date)" is just lazy. Please read https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue Change By: Daniel Beck (09/Feb/15 9:16 PM) Status: Open Resolved Resolution: Incomplete 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] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
Ximon Eighteen commented on JENKINS-26854 EC2 slave launch stops working after a while with AmazonServiceException Request has expired I've been looking at the underlying AWS SDK code and it looks like it already has built in support for refreshing the credentials before they expire, and that this support is already being used by the Jenkins EC2 plugin. The only things I can think of are either that NTP isn't working properly and clock drift causes the problem, or that the synchronous mode of credential refresh being used by the Jenkins EC2 plugin doesn't work for some reason and perhaps the asynchronous background thread mode needs to be used? I will investigate NTP on my side. 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-26420) Specifying sha1 without branch name in the notifyCommit URL triggers builds for all jobs (potentially hundreds)
Daniel Beck commented on JENKINS-26420 Specifying sha1 without branch name in the notifyCommit URL triggers builds for all jobs (potentially hundreds) Mark Waite: Resolve as incomplete as there's been no response to your comment in several weeks? 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] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Cletus DSouza edited a comment on JENKINS-26770 version 1.29 of the plugin does not work! I need the stacktrace from the logs when you click 'Apply' as the previous one you sent is related to a polling event. The jobConfigHistory/showDiffFiles doesn't seem to be a stock Jenkins thing as I don't it in my clean Jenkins setup. If you go to http://jenkins/job/Job_Name/changes that will get you to the stock Jenkins change history page. 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] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Cletus DSouza commented on JENKINS-26770 version 1.29 of the plugin does not work! The jobConfigHistory comes from another plugin - https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory+Plugin. Obviously, that plugin cannot compare old data of Integrity SCM to the new data. 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] [integrity-plugin] (JENKINS-26770) version 1.29 of the plugin does not work!
Cletus DSouza commented on JENKINS-26770 version 1.29 of the plugin does not work! The jobConfigHistory/showDiffFiles doesn't seem to be a stock Jenkins thing as I don't it in my clean Jenkins setup. If you go to http://jenkins/job/Job_Name/changes that will get you to the stock Jenkins change history page. 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-26782) Failure to wipeout workspace from an OSX slave due to unmappable characters
Daniel Beck commented on JENKINS-26782 Failure to wipeout workspace from an OSX slave due to unmappable characters What's the file.encoding on the OS X slave? LANG? Please provide the slave's system info (from /computer/slavename/systemInfo). 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-26780) Auto-installer for JDK no longer works
Daniel Beck commented on JENKINS-26780 Auto-installer for JDK no longer works Please attach the file JENKINS_HOME/updates/hudson.tools.JDKInstaller. 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-26782) Failure to wipeout workspace from an OSX slave due to unmappable characters
Nicolae Ghimbovschi commented on JENKINS-26782 Failure to wipeout workspace from an OSX slave due to unmappable characters TERM=xterm-256color SHELL=/bin/bash TMPDIR=/var/folders/xk/rth1rtgd6v96z_fvhq71vvvhgq/T/ LC_CTYPE=UTF-8 _=/usr/bin/env awt.toolkit sun.lwawt.macosx.LWCToolkit file.encoding US-ASCII file.encoding.pkg sun.io file.separator / ftp.nonProxyHosts local|.local|169.254/16|.169.254/16 gopherProxySet false http.nonProxyHosts local|.local|169.254/16|.169.254/16 java.awt.graphicsenv sun.awt.CGraphicsEnvironment java.awt.headless true java.awt.printerjob sun.lwawt.macosx.CPrinterJob java.class.path slave.jar java.class.version 51.0 java.endorsed.dirs /Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home/jre/lib/endorsed java.ext.dirs /Users/mobile_daily/Library/Java/Extensions:/Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home/jre/lib/ext:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java java.home /Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home/jre java.io.tmpdir /var/folders/xk/rth1rtgd6v96z_fvhq71vvvhgq/T/ java.library.path /Users/mobile_daily/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:. java.runtime.name Java(TM) SE Runtime Environment java.runtime.version 1.7.0_25-b15 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.7 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.7.0_25 java.vm.info mixed mode java.vm.name Java HotSpot(TM) 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.7 java.vm.vendor Oracle Corporation java.vm.version 23.25-b01 jna.platform.library.path /usr/lib:/usr/lib line.separator os.arch x86_64 os.name Mac OS X os.version 10.9.5 path.separator : socksNonProxyHosts local|.local|169.254/16|.169.254/16 sun.arch.data.model 64 sun.boot.class.path /Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home/jre/lib/resources.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home/jre/lib/rt.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home/jre/lib/sunrsasign.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home/jre/lib/jsse.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home/jre/lib/jce.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home/jre/lib/charsets.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home/jre/lib/jfr.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home/jre/lib/JObjC.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home/jre/classes sun.boot.library.path /Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home/jre/lib sun.cpu.endian little sun.cpu.isalist sun.font.fontmanager sun.font.CFontManager sun.io.unicode.encoding UnicodeBig sun.java.command slave.jar sun.java.launcher SUN_STANDARD sun.jnu.encoding US-ASCII sun.management.compiler HotSpot 64-Bit Tiered Compilers sun.os.patch.level unknown svnkit.http.methods Digest,Basic,NTLM,Negotiate svnkit.ssh2.persistent false user.country US user.dir /opt/dailybuild/jenkins user.home /Users/mobile_daily user.language en user.name mobile_daily user.timezone Europe/Chisinau 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] [remoting] (JENKINS-26855) Unreachable objects remoting.Channel can not garbage collect
denger tung updated JENKINS-26855 Unreachable objects remoting.Channel can not garbage collect Change By: denger tung (09/Feb/15 11:04 AM) Description: Myjenkinsserveroldgenerationis20GB,usethan90%,Itshouldtriggerfullgc,butseemslikeitdidnt.soidumptheheap,found10GB+remoting.Channelunreachableobjectsinheap. 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-26813) Missing configuration sections in freestyle multibranch projects
Daniel Beck resolved JENKINS-26813 as Not A Defect Missing configuration sections in freestyle multibranch projects As determined in your other report, this is in a component that does not use this Jira to track its issues. Change By: Daniel Beck (09/Feb/15 10:09 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-26782) Failure to wipeout workspace from an OSX slave due to unmappable characters
Daniel Beck resolved JENKINS-26782 as Not A Defect Failure to wipeout workspace from an OSX slave due to unmappable characters Fix this: file.encoding US-ASCII Change By: Daniel Beck (09/Feb/15 10:42 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-26782) Failure to wipeout workspace from an OSX slave due to unmappable characters
Nicolae Ghimbovschi commented on JENKINS-26782 Failure to wipeout workspace from an OSX slave due to unmappable characters Where can I change it ? In "JVM Options: -Dfile.encoding=UTF-8" for the Slave ? 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] [compress-artifacts-plugin] (JENKINS-26858) java.net.URISyntaxException when special chars are used in filename
Oliver Gondža
updated JENKINS-26858
java.net.URISyntaxException when special chars are used in filename
Change By:
Oliver Gondža
(09/Feb/15 10:55 AM)
Description:
Specialcharacterssuchas
{{
:
}}
,
{{\
[
}}
,
{{
]
}}
[JIRA] [core] (JENKINS-26857) Out Of Memory Error
Daniel Beck resolved JENKINS-26857 as Not A Defect Out Of Memory Error Your system does not have enough RAM to support Xmx4g. I generally don't go higher than half of total RAM on a server that runs no notable other software. Not a bug in Jenkins, your server configuration is just broken. This is an issue tracker, not a support site. Change By: Daniel Beck (09/Feb/15 10:07 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] [compress-artifacts-plugin] (JENKINS-26858) java.net.URISyntaxException when special chars are used in filename
Oliver Gondža
created JENKINS-26858
java.net.URISyntaxException when special chars are used in filename
Issue Type:
Bug
Assignee:
Oliver Gondža
Components:
compress-artifacts-plugin
Created:
09/Feb/15 10:46 AM
Description:
Special characters such as :, }}, {{ and possible others causes following exception whenever Build#getArtifacts() is called (on a build its artefacts are compressed):
javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: vfszip:/var/lib/jbossas/server/production/deploy/hudson.war/WEB-INF/lib/jenkins-core-1.532.3-4.7129fa4f.jar/hudson/model/Job/index.jelly:38:39: st:include java.net.URISyntaxException: Illegal character in scheme name at index 0: 2014-11-14_07:08:11/
at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117)
at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717)
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.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.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:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jenkinsci.plugins.reverse_proxy_auth.ReverseProxySecurityRealm$1.doFilter(ReverseProxySecurityRealm.java:142)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at
