[JIRA] [build-with-parameters] (JENKINS-18763) Disable Parameter-Elements by JavaScript does not work anymore
Sven Finsterwalder created JENKINS-18763 Disable Parameter-Elements by _javascript_ does not work anymore Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: jenkins_build_with_param.png, jenkins_insert_js.png Components: build-with-parameters Created: 16/Jul/13 6:07 AM Description: In our buildjob we have some parameters. Because we have so many parameter we have added a _javascript_ which preselects some parameter for us. But with the latest update to 1.522 it does not work anymore. We have insert the _javascript_ into a descriptionfield of a text-parameter as html (s. Screenshot) When we would start a build with parameter, only the first dropdown should be activated. After we have selected one value of the first dropdown the other dropdowns should be also activated. Project: Jenkins Priority: Major 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/groups/opt_out.
[JIRA] [buildresulttrigger] (JENKINS-18667) NullPointerException when saving job config
David Turner edited a comment on JENKINS-18667 NullPointerException when saving job config I have the same problem (GroovyScriptTrigger.getLogFile) trying to save job config. This is after updating Jenkins 1.504 to 1.523 and ScriptTrigger 0.23 to 0.29. SEVERE: Error while serving http://x:8080/jenkins/job//configSubmit java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ... at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.NullPointerException at org.jenkinsci.plugins.scripttrigger.groovy.GroovyScriptTrigger.getLogFile(GroovyScriptTrigger.java:77) at org.jenkinsci.plugins.scripttrigger.groovy.GroovyScriptTrigger.getProjectActions(GroovyScriptTrigger.java:71) ... at hudson.model.Project.submit(Project.java:202) at hudson.model.Job.doConfigSubmit(Job.java:1084) at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:765) ... 66 more Update: I have tried uninstalling ScriptTrigger v0.29 and reinstalling v0.28 and the last successful version v0.23, still getting the same NPE at GroovyScriptTrigger.java:77, so I suspect is is not an issue with the plugin. I will try to rollback Jenkins. Update: Rollback to 1.504 I can save job configs, but there are other issues now with some plugins dependant on a greater version, so I'll try and find a version in between. This is disappointing, I'll definitely be more cautious with updates in future. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [buildresulttrigger] (JENKINS-18667) NullPointerException when saving job config
Florian Doersch commented on JENKINS-18667 NullPointerException when saving job config 1.520 worked correctly for me with 0.28 (or perhaps even 0.29 idk) it seems that only matrix(/multi configuration)-jobs are affected. the NPE seems to be "job.getRootDir()" (either job is null or getRootDir returns null) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-10914) do not run incremental build in release build
Robert Kleinschmager assigned JENKINS-10914 to Robert Kleinschmager do not run incremental build in release build Change By: Robert Kleinschmager (16/Jul/13 6:57 AM) Assignee: teilo RobertKleinschmager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-18705) Team Concert Plugin is failing in a multi-configuration project
Julian Payne commented on JENKINS-18705 Team Concert Plugin is failing in a multi-configuration project I will look at your suggestions - thanks. However it seems to me that the problem is that the RTC plugin is doing a checkout in the root project and it is this checkout that is causing the problem? If you look at the trace that I sent you will see that the "configured sub-projects" are checking out the code correctly in a sub-project (but using the same workspace because that is how multi-configuration projects are defined in Jenkins). The nesting comes from the initial checkout in the root project by the RTC plugin which is superflous as we are not going to do any builds in the root project? Can you confirm that the multi-configuration project does work with the RTC plugin and if yes could you provide me with an example so that I can see what I am doing wrong in my configuration? Thanks again for your help. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [custom-tools] (JENKINS-18707) CustomTools plugin doesn't work properly on Multi-configuration builds
Oleg Nenashev started work on JENKINS-18707 CustomTools plugin doesnt work properly on Multi-configuration builds Change By: Oleg Nenashev (16/Jul/13 7:19 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/groups/opt_out.
[JIRA] [core] (JENKINS-16660) Environment variable replacement/resolving
Sven Appenrodt commented on JENKINS-16660 Environment variable replacement/resolving It is Thx This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [custom-tools] (JENKINS-18707) CustomTools plugin doesn't work properly on Multi-configuration builds
Oleg Nenashev updated JENKINS-18707 CustomTools plugin doesnt work properly on Multi-configuration builds Change By: Oleg Nenashev (16/Jul/13 8:55 AM) Issue Type: Bug NewFeature Description: Toolisbeinginstalledonthe master-job MatrixBuildandMatrixRunjobs ,but theresnomodificationofenvironmentvariables inthe configuration-jobs mostofcasestoolsarentrequiredattheMatrixBuild.Duetorandomnodeselection(w/oNodeLabelhack)ofMasterjob,installationatMatrixBuildcanfailduetounavailabilityoftool=itwouldbegreattohavedisableinstallationatmasterjoboption This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-10914) do not run incremental build in release build
Robert Kleinschmager commented on JENKINS-10914 do not run incremental build in release build submitted pull request https://github.com/jenkinsci/m2release-plugin/pull/12 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-10914) do not run incremental build in release build
Robert Kleinschmager started work on JENKINS-10914 do not run incremental build in release build Change By: Robert Kleinschmager (16/Jul/13 9:01 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/groups/opt_out.
[JIRA] [urltrigger] (JENKINS-18764) NPE in URLTrigger when saving project configuration
Jens Hausherr created JENKINS-18764 NPE in URLTrigger when saving project configuration Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: urltrigger Created: 16/Jul/13 9:16 AM Description: When saving a project configuration a NullPointerException occurs in UrlTrigger.getLogFile(). javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:726) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:586) at org.kohsuke.stapler.Stapler.service(Stapler.java:217) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) 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:118) 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 org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:47) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at
[JIRA] [all-changes] (JENKINS-18677) Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers
Stefan Hirche commented on JENKINS-18677 Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers So is this a problem in the plugins, as I get the same issue with the ivy plugin, but there is no new version of it. java.lang.NoSuchFieldError: triggers at hudson.ivy.AbstractIvyProject.createTransientActions(AbstractIvyProject.java:62) at hudson.ivy.IvyModuleSet.createTransientActions(IvyModuleSet.java:251) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:724) at hudson.ivy.IvyModuleSet.updateTransientActions(IvyModuleSet.java:246) at hudson.model.AbstractProject.onLoad(AbstractProject.java:322) at hudson.ivy.IvyModuleSet.onLoad(IvyModuleSet.java:520) at hudson.model.Items.load(Items.java:221) at jenkins.model.Jenkins$18.run(Jenkins.java:2553) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskG... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-18553) configuration is lost, and no new configuration possible
Skuli Arnlaugsson commented on JENKINS-18553 configuration is lost, and no new configuration possible Same here, fixed after 1.3.5 update - note that the configuration (start/initial job for example) is still lost, but adding them again fixes the view. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh] (JENKINS-18765) SSH key exchange is failing, but ssh from command prompt is working
Dinesh S created JENKINS-18765 SSH key exchange is failing, but ssh from command prompt is working Issue Type: Bug Assignee: Unassigned Components: ssh Created: 16/Jul/13 9:47 AM Description: i am using Host authentication (private/public key authentication) in the SSH plugin to connect from our master build server to our UAT server. The userid defined on our UAT server is a non interactive user. When I provide that userid in the SSH Credentials, it treats the user as an interactive user and as a result the key exchange fails. Is there a way to mark this user as a non-interactive user in Jenkins? Project: Jenkins Priority: Major Reporter: Dinesh S This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cli] (JENKINS-18766) update-job from cli doesn't update Root POM from anything to pom.xml
bruce zhang created JENKINS-18766 update-job from cli doesnt update Root POM from anything to pom.xml Issue Type: Bug Assignee: SCM/JIRA link daemon Components: cli Created: 16/Jul/13 9:57 AM Description: Demo step by step: Step1: creat a job as maven2/3 project Step2: make a copy of the job's config.xml as config-old.xml Step3: update "Root POM" of the job from UI to "pom-new.xml" Step4: update the job using "update-job" CLI Command with config-old.xml Step5: Checking (1) from the backend, the config.xml is the same as config-old.xml! (2) from the UI side, it's "pom-new.xml"! Step6: reload configuration of Jenkins, back to normal! So, we got it! "update-job" CLI command has a bug when update "Root POM", just like change the config.xml directly. Project: Jenkins Labels: cli update-job Priority: Major Reporter: bruce zhang This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [redmine] (JENKINS-18312) changelog browsing uses the wrong path to Redmine
sogabe commented on JENKINS-18312 changelog browsing uses the wrong path to Redmine @gaooh, The maintainer of this plugin will merge pull requests this weekend. Just wait. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [redmine] (JENKINS-18312) changelog browsing uses the wrong path to Redmine
sogabe edited a comment on JENKINS-18312 changelog browsing uses the wrong path to Redmine @gaooh, The maintainer of this plugin will merge pull requests this weekend. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18715) scandir being triggered by FingerPrint.save
Hua Zhang commented on JENKINS-18715 scandir being triggered by FingerPrint.save Seems to me that the PR improves the performance a lot. At least for my situation, I cannot recognise the difference between with and without the include pattern. On the other hand, I also cannot confirm whether scandir still be triggered by the fingerprinting, or it is just fast enough. Anyway, the performance problem is gone. Thanks for the quick fix! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18715) scandir being triggered by FingerPrint.save
Hua Zhang commented on JENKINS-18715 scandir being triggered by FingerPrint.save Please feel free to close the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-18759) Build Pipeline Plugin no longer maintaining parameters on Retry
Skuli Arnlaugsson commented on JENKINS-18759 Build Pipeline Plugin no longer maintaining parameters on Retry Still an issue on 1.3.5. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [selenium] (JENKINS-18638) Selenium Plugin New Configuration error: 'config.jelly' for class hudson.plugins.selenium.configuration.browser.selenium.IEBrowser
Mustafa Lodhi commented on JENKINS-18638 Selenium Plugin New Configuration error: config.jelly for class hudson.plugins.selenium.configuration.browser.selenium.IEBrowser I have done a setup of Jenkins 1.522 and facing the same issue. Can any help in resolving this issue as early as possible. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [selenium] (JENKINS-18638) Selenium Plugin New Configuration error: 'config.jelly' for class hudson.plugins.selenium.configuration.browser.selenium.IEBrowser
Mustafa Lodhi edited a comment on JENKINS-18638 Selenium Plugin New Configuration error: config.jelly for class hudson.plugins.selenium.configuration.browser.selenium.IEBrowser I have done a setup of Jenkins 1.522 and facing the same issue. Can any one help in resolving this issue as early as possible. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-18767) Checking java version fails - SSH slave not connecting
Waldek M created JENKINS-18767 Checking java version fails - SSH slave not connecting Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: ssh-slaves Created: 16/Jul/13 11:35 AM Description: I've seen the issue as resolved (at least twice), but it still occurs for me. Despite having Java binary on slave and master, the SSH Slave plugin fails to find Java version. Error log: 07/16/13 10:48:00 SSH Opening SSH connection to ...:22. 07/16/13 10:48:00 SSH Authentication successful. 07/16/13 10:48:00 SSH The remote users environment is: 07/16/13 10:48:00 SSH Checking java version of java Couldn't figure out the Java version of java 07/16/13 10:48:00 SSH Checking java version of /usr/bin/java Couldn't figure out the Java version of /usr/bin/java 07/16/13 10:48:00 SSH Checking java version of /usr/java/default/bin/java Couldn't figure out the Java version of /usr/java/default/bin/java 07/16/13 10:48:00 SSH Checking java version of /usr/java/latest/bin/java Couldn't figure out the Java version of /usr/java/latest/bin/java 07/16/13 10:48:00 SSH Checking java version of /usr/local/bin/java Couldn't figure out the Java version of /usr/local/bin/java 07/16/13 10:48:00 SSH Checking java version of /usr/local/java/bin/java Couldn't figure out the Java version of /usr/local/java/bin/java 07/16/13 10:48:00 SSH Checking java version of /bin/java Couldn't figure out the Java version of /bin/java hudson.util.IOException2: Could not find any known supported java version in java, /usr/bin/java, /usr/java/default/bin/java, /usr/java/latest/bin/java, /usr/local/bin/java, /usr/local/java/bin/java, /bin/java, and we also failed to install JDK as a fallback at hudson.plugins.sshslaves.SSHLauncher.resolveJava(SSHLauncher.java:557) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:493) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:230) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.io.IOException: Failed to detect the environment for automatic JDK installation. Please report this to jenkinsci-us...@googlegroups.com: at hudson.plugins.sshslaves.SSHLauncher.attemptToInstallJDK(SSHLauncher.java:654) at hudson.plugins.sshslaves.SSHLauncher.resolveJava(SSHLauncher.java:555) ... 7 more 07/16/13 10:48:00 SSH Connection closed. Environment: Linux (RHEL master + Ubuntu slave) Project: Jenkins Priority: Major Reporter: Waldek M This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-10317) Gerrit Trigger 2.3.0 job specific Gerrit Reporting Values and job specifc Custom Build Messages does not work.
alan martinovic commented on JENKINS-10317 Gerrit Trigger 2.3.0 job specific Gerrit Reporting Values and job specifc Custom Build Messages does not work. I can confirm the existence of this issue in gerrit-trigger 2.10.1 Setting a job specific custom build message for starting a build stops start messages form appearing in comments in Gerrit. (Jenkins- job name - Configure - Gerrit trigger - Custom Build Messages - Advanced - Custom Build Messages - Build Start Messages) If they are left blank, the message is generated based on the global configuration for the start message. (Jenkins - Manage Jenkins - Gerrit Trigger - Advanced - Gerrit Verified Commands - Started) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
CARTA DE SERVIÇOS | Cód. 96
PREZADO CLIENTE : PERDEU OS DADOS, NÃO SE PREOCUPE, NÓS RECUPERAMOS PARA VOCE. EMPRESA ESPECIALIZADA EM RECUPERAÇÃO PROFISSIONAL E MANUTENÇÃO ASSISTËNCIA TÉCNICA EM DADOS DE.DADOS EM SERVIDORES DE P/M/G PORTE DADOS EM RAIDS 0/1/5/10DADOS EM CDR E DVDSDADOS EM FILMADORASDADOS EM MAQ.DIGITAISDADOS EM PEN DRIVESDADOS EM HDS MAQ.INDUSTRAISE OUTROS:DICA: Não se desespere e não entregue seu hd a pessoas que não tenha capacitada e técnica no resgate dos dados não use técnicas amadoras que só fazem forçar a cabeça e riscar a mídia do hd existem muitos progra- minhas gratuitos de internet que só fazem piorar a situação do hd, quanto a perfeição dos dados.(VALORES A PARTIR DE R$:250,00 - REAIS PARA O SERVIÇONÃO COBRAMOS O DIAGNOSTICO E ORÇAMENTO) Faça Sua Recuperação De Dados e Pague Com, Cartão de Crédito,Bole to Bancário da Caixa Economica Federal,de 0 a 12 vezes com preço fixo com entrada de ?%-( dependendo do valor do serviço ), ou Déposito Em Conta Corrente. Trabalhamos para Pessoas Físicas,Júridicas,e orgãos públicos Matriz Londrina:(43)9622.4505(43)3323.8292Emails:cont...@sosdatarecovery.com.brFilial em Brasilia:(61)8149.8032(61)3556.4499 Email:escritoriobrasi...@sosdatarecovery.com.brRep.Recife:(81)3453.0675(81)8840.6621(81)9997.6601 Email:gmcbr...@ig.com.br-gibson.br...@uol.com.br -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. Adjunto: HD IDE 113.jpg
[JIRA] [jenkins-multijob-plugin] (JENKINS-18768) Multijob plugin doesn't aggregate test results from downstream projects
Aleksey Alekseev created JENKINS-18768 Multijob plugin doesnt aggregate test results from downstream projects Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jenkins-multijob-plugin Created: 16/Jul/13 12:23 PM Description: I have configured multijob project to execute parallel build on two slave jenkins nodes. But when build finished I can't see aggregate test results. Environment: jenkins 1.520 multijob-plugin 1.9 Project: Jenkins Labels: plugin jenkins multijob slaves master Priority: Major Reporter: Aleksey Alekseev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh] (JENKINS-18765) SSH key exchange is failing, but ssh from command prompt is working
Dinesh S commented on JENKINS-18765 SSH key exchange is failing, but ssh from command prompt is working When i specify the key path and click "Test Configuration", I see the error "jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message invalid privatekey: TheKey". However I am sure the key path is correct as I am able to connect via SSH using command prompt and can be verified via the logs in /var/log/messages. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-18725) Builds are failing after upgrade to 1.522
Dinesh S closed JENKINS-18725 as Fixed Builds are failing after upgrade to 1.522 got fixed on its own Change By: Dinesh S (16/Jul/13 12:39 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-with-parameters] (JENKINS-18763) Disable Parameter-Elements by JavaScript does not work anymore
Sven Finsterwalder updated JENKINS-18763 Disable Parameter-Elements by _javascript_ does not work anymore Change By: Sven Finsterwalder (16/Jul/13 12:47 PM) Attachment: jenkins_build_with_param.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/groups/opt_out.
[JIRA] [ssh] (JENKINS-18769) SSH Publish Plugin - Unable to use the private key provided in the key path
Dinesh S created JENKINS-18769 SSH Publish Plugin - Unable to use the private key provided in the key path Issue Type: Bug Assignee: Unassigned Components: ssh Created: 16/Jul/13 12:59 PM Description: We use SSH Tectia for our SSH connectivity. In my Jenkins job, i have provided the userid (destination) and the private keyfile (absolute path in the Source box). When i try to test the configuration it fails with the below exception Failed to connect or change directory jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message invalid privatekey: TheKey But the same connection id works through command prompt and i can see the keyfile is the same that i have provided. Project: Jenkins Priority: Major Reporter: Dinesh S This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18689) slave unstable become online and offline
daniel anggrianto commented on JENKINS-18689 slave unstable become online and offline our slaves were disconnected as well and this is the error log that we are getting Jul 15, 2013 5:51:29 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Terminated Jul 15, 2013 5:52:42 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among [http://mario.icims.net:8181/jenkins/] Jul 15, 2013 5:52:42 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to mario.icims.net:56232 Jul 15, 2013 5:52:42 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking Jul 15, 2013 5:52:47 PM hudson.remoting.jnlp.Main$CuiListener error SEVERE: unexpected stream termination java.io.EOFException: unexpected stream termination at hudson.remoting.ClassicCommandTransport.create(ClassicCommandTransport.java:100) at hudson.remoting.Channel.init(Channel.java:392) at hudson.remoting.Channel.init(Channel.java:388) at hudson.remoting.Channel.init(Channel.java:349) at hudson.remoting.Channel.init(Channel.java:345) at hudson.remoting.Channel.init(Channel.java:333) at hudson.remoting.Engine.run(Engine.java:237) Jul 16, 2013 8:52:02 AM hudson.remoting.jnlp.Main$CuiListener init INFO: Jenkins agent is running in headless mode. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
sogabe assigned JENKINS-17885 to bap Publish over SSH lost main configuration data after jenkins server reboot Change By: sogabe (16/Jul/13 1:08 PM) Assignee: bap This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [eloyente] (JENKINS-18770) ElOyente plugin blocks jenkins configuration page
Nicolas Rosa created JENKINS-18770 ElOyente plugin blocks jenkins configuration page Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: eloyente Created: 16/Jul/13 1:08 PM Description: After installation any change to the global config of Jenkins result in an error. Only workaround is to disable eloyente and restart jenkins, do the modification and then re-enable eloyente and restart again jenkins. Environment: Jenkins 1.509.1 on linux (ubuntu 12.04) Project: Jenkins Labels: plugin Priority: Major Reporter: Nicolas Rosa This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-15935) Can't build using maven 3.1.0 latest release candidate
edbras commented on JENKINS-15935 Cant build using maven 3.1.0 latest release candidate Having the same problem after upgrading to Maven 3.1.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/groups/opt_out.
[JIRA] [custom-tools] (JENKINS-18771) Add descriptions for custom tools
Oleg Nenashev created JENKINS-18771 Add descriptions for custom tools Issue Type: New Feature Assignee: Oleg Nenashev Components: custom-tools, customtools-plugin Created: 16/Jul/13 1:30 PM Project: Jenkins Priority: Major Reporter: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [custom-tools] (JENKINS-18772) Add support of versions to the custom tools
Oleg Nenashev created JENKINS-18772 Add support of versions to the custom tools Issue Type: New Feature Assignee: Oleg Nenashev Components: custom-tools, customtools-plugin Created: 16/Jul/13 1:31 PM Project: Jenkins Priority: Major Reporter: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-18711) Multiline warning should result in multiple warnings
Johannes Heger commented on JENKINS-18711 Multiline warning should result in multiple warnings Downloaded the source code and I think it make sense to write a new plugin (low prio). Kind regards, Johannes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobcopy-builder] (JENKINS-18773) Copy Operation for adding new job to View
Thomas Vestergaard Trolle created JENKINS-18773 Copy Operation for adding new job to View Issue Type: New Feature Assignee: Unassigned Components: jobcopy-builder Created: 16/Jul/13 1:49 PM Description: When copying a job, it would be highly attractive to also be able to add the new job to an existing view, so as the developers does not have to do this manually. I can't imagine, we are the only shop with many teams/projects/etc. using the same Jenkins server, where it is necessary to keep your jobs organised in Views to have easy access to them for tracking of changes/status/etc., as the "All" view contains way too many other jobs. Project: Jenkins Labels: plugin Priority: Major Reporter: Thomas Vestergaard Trolle This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobcopy-builder] (JENKINS-18773) Copy Operation for adding new job to View
Thomas Vestergaard Trolle commented on JENKINS-18773 Copy Operation for adding new job to View I will try and see if I can make a patch/pull request implementing this - implementing the extension as a seperate plugin seems like overkill... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [custom-tools] (JENKINS-18774) Add setup of additional variables after installation
Oleg Nenashev created JENKINS-18774 Add setup of additional variables after installation Issue Type: New Feature Assignee: Oleg Nenashev Components: custom-tools, customtools-plugin Created: 16/Jul/13 2:54 PM Description: It should be possible to list variables in the installer or specify prop file from the installation script Project: Jenkins Priority: Major Reporter: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18775) [XStream] ConcurrentModificationException from DefaultConverterLookup
Jesse Glick created JENKINS-18775 [XStream] ConcurrentModificationException from DefaultConverterLookup Issue Type: Bug Assignee: Jesse Glick Components: core Created: 16/Jul/13 2:57 PM Description: A user reported a hung Jenkins instance displaying an error: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246) at jenkins.InitReactorRunner.run(InitReactorRunner.java:43) at jenkins.model.Jenkins.executeReactor(Jenkins.java:904) at jenkins.model.Jenkins.init(Jenkins.java:804) at hudson.model.Hudson.init(Hudson.java:81) at hudson.model.Hudson.init(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:214) Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.InitializerFinder.invoke(InitializerFinder.java:124) at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:893) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) ... 8 more Caused by: java.util.ConcurrentModificationException at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1115) at java.util.TreeMap$KeyIterator.next(TreeMap.java:1169) at com.thoughtworks.xstream.core.util.PrioritizedList$PrioritizedItemIterator.next(PrioritizedList.java:91) at com.thoughtworks.xstream.core.DefaultConverterLookup.lookupConverterForType(DefaultConverterLookup.java:55) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:56) Seems that DefaultConverterLookup is failing to synchronize access to its converters field; probably another thread was calling registerConverter in the middle of this loop. Environment: 1.516; JDK 7u10; Linux Project: Jenkins Labels: threads xstream Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven2] (JENKINS-10539) windows path separators not correctly escaped in Maven properties configuration
Oliver Gondža commented on JENKINS-10539 windows path separators not correctly escaped in Maven properties configuration PR: https://github.com/jenkinsci/jenkins/pull/841 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16095) Heap memory leak (possibly jclouds plugin related)
Jesse Glick updated JENKINS-16095 Heap memory leak (possibly jclouds plugin related) Change By: Jesse Glick (16/Jul/13 3:19 PM) Labels: memory-leakperformance This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18776) @QueryParameter with @RelativePath broken
Kohsuke Kawaguchi created JENKINS-18776 @QueryParameter with @RelativePath broken Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: core Created: 16/Jul/13 3:42 PM Description: a stapler change in 1.208 broke the @InjectedParameter annotation handling. When non-injected annotation (such as @RelativePath) annotation is present, it'll mask the handling of the injected annotation (such as @QueryParameter.) Project: Jenkins Priority: Critical Reporter: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
Jesse Glick updated JENKINS-18641 People View does Not Populate (makeStaplerProxy) Change By: Jesse Glick (16/Jul/13 3:48 PM) Labels: jenkinsuser regressionstapler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
Jesse Glick commented on JENKINS-18641 People View does Not Populate (makeStaplerProxy) 1.521 introduced Stapler 1.213 with: https://github.com/stapler/stapler/commit/48cdf0f3242c6a79bb398e9115c0db7526c42a50 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
Jesse Glick assigned JENKINS-18641 to Jesse Glick People View does Not Populate (makeStaplerProxy) Change By: Jesse Glick (16/Jul/13 3:50 PM) Assignee: JesseGlick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
Shannon Kerr commented on JENKINS-18641 People View does Not Populate (makeStaplerProxy) Jesse, I thought we first saw this behavior in the 1.520 release though? I can go back and try it again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18776) @QueryParameter with @RelativePath broken
Jesse Glick updated JENKINS-18776 @QueryParameter with @RelativePath broken Change By: Jesse Glick (16/Jul/13 4:15 PM) Labels: lts-candidate regression This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18776) @QueryParameter with @RelativePath broken
Jesse Glick commented on JENKINS-18776 @QueryParameter with @RelativePath broken Should be easy enough to write a regression test for this, right? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18777) Expose job build schedules in Remote API
Nathan Malinoski created JENKINS-18777 Expose job build schedules in Remote API Issue Type: Improvement Assignee: Unassigned Components: core Created: 16/Jul/13 4:45 PM Description: If a job has the Build Periodically field configured, please expose that field's value, or perhaps a list of upcoming build times, via the Remote API. I understand I can get the value of Build Periodically (hudson.triggers.TimerTrigger/spec) by using the Extended Read Permission plugin, which can grant my service account access to a job's config.xml; however, I think it would be simpler and faster if jobs' schedules were available via the API. If I'm already communicating via XML, config.xml would just be another file that my code would need to retrieve and parse; but if I'm using JSON, I'd have to bloat my code with an XML parser just to grab a single value. Environment: RHEL 6, Jenkins installed via pkg.jenkins-ci.org repo Project: Jenkins Priority: Minor Reporter: Nathan Malinoski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
Jesse Glick commented on JENKINS-18641 People View does Not Populate (makeStaplerProxy) Nope, 1.520 works. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
Jesse Glick edited a comment on JENKINS-18641 People View does Not Populate (makeStaplerProxy) Not sure. Cannot reproduce even in trunk on Chrome. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
Shannon Kerr commented on JENKINS-18641 People View does Not Populate (makeStaplerProxy) OK, I'm still on 1.518 (there was another bug in 519 that I'm avoiding). Can anyone confirm that 1.523 does not have this problem any longer? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18778) Builds disappear from build history
Dominic Lam created JENKINS-18778 Builds disappear from build history Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 16/Jul/13 5:04 PM Description: We have 4-5 projects (out of ~40 projects) that all the builds disappear from the "Build History" from time to time. There was no external event (like restarting Jenkins, or triggering a new build for those projects). We know those builds are there from the Jobs directory, but they just don't show on the Build history. Only after we restart Jenkins, and after restart the builds come to the build history. Environment: Jenkins 1.521 Project: Jenkins Priority: Critical Reporter: Dominic Lam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18778) Builds disappear from build history
Dominic Lam updated JENKINS-18778 Builds disappear from build history Change By: Dominic Lam (16/Jul/13 5:07 PM) Attachment: screenshot-3.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/groups/opt_out.
[JIRA] [core] (JENKINS-18778) Builds disappear from build history
Dominic Lam updated JENKINS-18778 Builds disappear from build history Change By: Dominic Lam (16/Jul/13 5:07 PM) Attachment: screenshot-2.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/groups/opt_out.
[JIRA] [core] (JENKINS-18778) Builds disappear from build history
Dominic Lam updated JENKINS-18778 Builds disappear from build history Change By: Dominic Lam (16/Jul/13 5:06 PM) Attachment: screenshot-1.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/groups/opt_out.
[JIRA] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
Jesse Glick assigned JENKINS-18641 to ssogabe People View does Not Populate (makeStaplerProxy) Cannot work on this if I cannot reproduce the problem to begin with. Change By: Jesse Glick (16/Jul/13 5:09 PM) Assignee: JesseGlick ssogabe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
Jesse Glick edited a comment on JENKINS-18641 People View does Not Populate (makeStaplerProxy) Not sure. Cannot reproduce even in trunk on Chrome on Linux. Wrote an HTMLUnit test for it, but that passes in trunk too. Perhaps the script tag is only inserted under certain circumstances? Display seems broken in IE 8, but that appears to be a different problem (in sortable.js), present even in 1.509.2. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17174) Javascript proxy failes when sending html/xml formated messages
Jesse Glick resolved JENKINS-17174 as Duplicate _javascript_ proxy failes when sending html/xml formated messages Seems to have been fixed in 1.506, presumably by json-lib upgrade. Change By: Jesse Glick (16/Jul/13 5:34 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
dogfood commented on JENKINS-18641 People View does Not Populate (makeStaplerProxy) Integrated in jenkins_main_trunk #2716 JENKINS-18641 Test passing in 1.520. (Revision 50c2bb39008d2da60a957b2c8b5ef7d8e09802cc) Result = SUCCESS Jesse Glick : 50c2bb39008d2da60a957b2c8b5ef7d8e09802cc Files : test/src/test/java/hudson/model/AsynchPeopleTest.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [artifactdeployer] (JENKINS-18135) Conditional Build Step plugin crashes when using Artifact Deployer plugin as build step
domi commented on JENKINS-18135 Conditional Build Step plugin crashes when using Artifact Deployer plugin as build step believe me, its not the intention to have the two behave different! Do you have this plugin installed too? https://wiki.jenkins-ci.org/display/JENKINS/Any+Build+Step+Plugin and then you have the global "Allowed build steps" option set to "Any build step"? ...with this configuration I can reproduce the issue - I don't know the "Any Build Step" plugin very well, but I will lock at it... If this is not your configuration, then please let me know how you can reproduce the issue when starting with a fresh jenkins installation This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-14301) Failed to use multiple update sites (plugin repositories)
evernat commented on JENKINS-14301 Failed to use multiple update sites (plugin repositories) Is it still an issue with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [artifactdeployer] (JENKINS-18135) Conditional Build Step plugin crashes when using Artifact Deployer plugin as build step
Kevin Phillips commented on JENKINS-18135 Conditional Build Step plugin crashes when using Artifact Deployer plugin as build step Sorry if my last comment sounded condescending ... that wasn't my intention Anyways, you are correct. I do have the Any Build Step plugin installed as well... maybe that is the one that allowed me to hook the Artifact Deployer as a Conditional Build Step. It will take me some time to setup a clean install of Jenkins to create a minimal reproducible environment, but it sounds like you may have already managed to reproduce the critical pieces that I am using. I have several dozen plugins installed atm so it would be hard for me to isolate which ones are possibly interacting with each other at this point, but I will see what I can do. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [config-file-provider] (JENKINS-15976) Provided maven settings.xml in maven builder is lost
dogfood commented on JENKINS-15976 Provided maven settings.xml in maven builder is lost Integrated in jenkins_main_trunk #2717 FIXES JENKINS-15976 After de-serializing changed job settings after "Save", the maven settings done by config-file-provider-plugin were overwritten blindly (presumably with fallback values). These fallback values should be set correctly in the constructor of the "Maven" class and do not need to be set explicitly after deserialization. (Revision 40f3b095aae871589b296e455dfad04f368c3dc3) FIXED JENKINS-15976 update changelog (Revision 5a3d877164e37554fa93eb9c5f011b6001d23956) Result = SUCCESS bastian.gloeckle : 40f3b095aae871589b296e455dfad04f368c3dc3 Files : core/src/main/java/hudson/tasks/Maven.java imod : 5a3d877164e37554fa93eb9c5f011b6001d23956 Files : changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18776) @QueryParameter with @RelativePath broken
Kohsuke Kawaguchi commented on JENKINS-18776 @QueryParameter with @RelativePath broken Hmm, it looks like the SCM/issue link daemon has stopped working. This fix is integrated toward 1.525. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18776) @QueryParameter with @RelativePath broken
Kohsuke Kawaguchi resolved JENKINS-18776 as Fixed @QueryParameter with @RelativePath broken Change By: Kohsuke Kawaguchi (16/Jul/13 7:35 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-13835) E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request
centic commented on JENKINS-13835 E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request So either the Garbage Collector that you run is not ideal for your type of load or you have enough memory, but just barely enough and because of this the GC needs to do lots of work to make some memory available. In the first case a look at some garbage collection tuning will help, in the second a bit more memory might do the trick. Looking at the Java VM with jvisualvm can give you an idea how memory of the application looks like and which solution might give better results. Maybe you can provide some facts, e.g. actual memory settings and what the memory graphs look like. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-timeout] (JENKINS-9716) allow timeouts to occur during pre-build
Devin Barbieri commented on JENKINS-9716 allow timeouts to occur during pre-build That just happened to me too, my job has a 7 hour timeout, but it sat there in the pre build, possibly scm, stage for 18 hours before having to be manually aborted. On the left you can see the elapsed time. 00:00:00.000 Started by upstream project "management-packaging" build number 1911 00:00:00.000 originally caused by: 00:00:00.000 Started by upstream project "management-setup.build" build number 1992 00:00:00.000 originally caused by: 00:00:00.000 Started by upstream project "management-begin.build.radon" build number 91 00:00:00.001 originally caused by: 00:00:00.001Started by an SCM change 00:00:00.001 Building remotely on bld-srv-16 in workspace /jenkins/workspace/management-radon-packaging/node/nbuild_mgmt_suse 18:43:45.466 Build was aborted 18:43:45.467 Aborted by Devin Barbieri dbarbi...@fusionio.com 18:44:07.591 ERROR: Publisher hudson.plugins.descriptionsetter.DescriptionSetterPublisher aborted due to exception 18:44:07.591 java.lang.InterruptedException This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
Jesse Glick commented on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException http://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/1.509.2.JENKINS-14362-jzlib/jenkins-war-1.509.2.JENKINS-14362-jzlib.war now also available if anyone using LTS thinks they are running into this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [conditional-buildstep] (JENKINS-17576) Conditional buildstep unable to launch MultiJob
domi commented on JENKINS-17576 Conditional buildstep unable to launch MultiJob any feedback on this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-18459) IOException: No Such File
Timo Boewing commented on JENKINS-18459 IOException: No Such File I can confirm the very same issue. Jenkins is running as WAR in Tomcat7 on Ubuntu. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [logging] (JENKINS-18780) Renaming Project causes content encoding error
Dennis McCurdy created JENKINS-18780 Renaming Project causes content encoding error Issue Type: Bug Affects Versions: current Assignee: Praqma Support Components: logging Created: 16/Jul/13 8:56 PM Description: Renaming a project causes a content encoding error page when hitting the save or apply button. The stack dump is as follows: SEVERE: Error while serving http://jenkinsurl:8080/view/Install/job/InstallCodedUITest/configSubmit java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor1051.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:297) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:160) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:95) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:586) at org.kohsuke.stapler.Stapler.service(Stapler.java:217) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) ... Caused by: java.lang.NullPointerException at org.jenkinsci.plugins.fstrigger.triggers.FileNameTrigger.getLogFile(FileNameTrigger.java:65) at org.jenkinsci.plugins.fstrigger.triggers.FileNameTrigger.getProjectActions(FileNameTrigger.java:287) at hudson.model.Project.createTransientActions(Project.java:222) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:724) at hudson.model.AbstractProject.save(AbstractProject.java:279) at hudson.model.AbstractItem.setDisplayName(AbstractItem.java:156) at hudson.model.Job.doConfigSubmit(Job.java:1069) at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:765) ... 76 more Due Date: 31/Jul/13 12:00 AM Environment: Updated to 1.523 on Ubuntu running on Windows nodes. Fix Versions: current Project: Jenkins Labels: winstone Priority: Major Reporter: Dennis McCurdy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe
[JIRA] [email-ext] (JENKINS-18779) Jenkins slaves should have the ability to specify the FROM field
Bassam Khouri created JENKINS-18779 Jenkins slaves should have the ability to specify the FROM field Issue Type: New Feature Assignee: Alex Earl Components: email-ext Created: 16/Jul/13 8:55 PM Description: In my jenkins configuration, I have a masters jenkins and multiple slaves. When a job runs on a slave, an email is currently sent from the Master jenkins system administrator email address. I would like the ability to have the email notificaiton "FROM" field to be customizeable based on which slave the project is built on. For example: slave #1 xould be configured to send email from a...@something.com slave #2 could be configured to send email from u...@here.com Project A runs on slave #1.. email sent from a...@something.com Project A runs on slave #2.. email sent from u...@here.com Project: Jenkins Priority: Major Reporter: Bassam Khouri This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [conditional-buildstep] (JENKINS-18762) Build number environment variable is not propagated when run inside a conditional build step
domi assigned JENKINS-18762 to Jesse Glick Build number environment variable is not propagated when run inside a conditional build step I think the issue is in the artifactcopy plugin at CopyArtifact.onStarted() : https://github.com/jenkinsci/copyartifact-plugin/blob/master/src/main/java/hudson/plugins/copyartifact/CopyArtifact.java#L376-L379 This method will not find a CopyArtifact.class in the BuildersList, as in our case the objects are wrapped in the 'org.jenkinsci.plugins.conditionalbuildstep.BuilderChain' and/or 'org.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder' don't know how to fix this yet, therefore assigning it to the maintainer of the copyartifact plugin, maybe Jesse has an idea... Change By: domi (16/Jul/13 9:07 PM) Assignee: domi JesseGlick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18779) Jenkins slaves should have the ability to specify the FROM field
Alex Earl resolved JENKINS-18779 as Wont Fix Jenkins slaves should have the ability to specify the FROM field This is not within the scope of email-ext. Change By: Alex Earl (16/Jul/13 9:07 PM) 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/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-18705) Team Concert Plugin is failing in a multi-configuration project
Heather Fraser-Dube commented on JENKINS-18705 Team Concert Plugin is failing in a multi-configuration project I see your point. I have been looking into this more. I am not sure how you configure a matrix build not to load in the root project, just in the sub project. Can you help me understand your matrix build configuration (so I can sort of replicate)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [conditional-buildstep] (JENKINS-18762) Build number environment variable is not propagated when run inside a conditional build step
domi edited a comment on JENKINS-18762 Build number environment variable is not propagated when run inside a conditional build step I think the issue is in the copyartifact plugin at CopyArtifact.onStarted() : https://github.com/jenkinsci/copyartifact-plugin/blob/master/src/main/java/hudson/plugins/copyartifact/CopyArtifact.java#L376-L379 This method will not find a CopyArtifact.class in the BuildersList, as in our case the objects are wrapped in the 'org.jenkinsci.plugins.conditionalbuildstep.BuilderChain' and/or 'org.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder' don't know how to fix this yet, therefore assigning it to the maintainer of the copyartifact plugin, maybe Jesse has an 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18779) Jenkins slaves should have the ability to specify the FROM field
Alex Earl commented on JENKINS-18779 Jenkins slaves should have the ability to specify the FROM field You can do this with a pre-send script if you wanted, it will not be implemented in the 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18779) Jenkins slaves should have the ability to specify the FROM field
Bassam Khouri commented on JENKINS-18779 Jenkins slaves should have the ability to specify the FROM field Do you know which component I need to direct my request to? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18779) Jenkins slaves should have the ability to specify the FROM field
Bassam Khouri commented on JENKINS-18779 Jenkins slaves should have the ability to specify the FROM field Can you provide me with a HOWTO link on how I can do this with a pre-send script? (I'm new to Jenkins) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18779) Jenkins slaves should have the ability to specify the FROM field
Alex Earl commented on JENKINS-18779 Jenkins slaves should have the ability to specify the FROM field Check the jenkins wiki, it has information about the pre-send script, so does the mailing list and the help directly in Jenkins for the plugin (see the ? icons). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18779) Jenkins slaves should have the ability to specify the FROM field
Alex Earl commented on JENKINS-18779 Jenkins slaves should have the ability to specify the FROM field It would have to be part of email-ext, but I won't implement it because you can do it other ways. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [conditional-buildstep] (JENKINS-18762) Build number environment variable is not propagated when run inside a conditional build step
Jesse Glick assigned JENKINS-18762 to domi Build number environment variable is not propagated when run inside a conditional build step I am not really the maintainer of this plugin (nor do I have any idea how to fix this bug with current Jenkins APIs). Change By: Jesse Glick (16/Jul/13 9:17 PM) Assignee: JesseGlick domi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18779) Jenkins slaves should have the ability to specify the FROM field
Bassam Khouri
commented on JENKINS-18779
Jenkins slaves should have the ability to specify the FROM field
I found the answer on this page: http://jenkins-ci.361315.n4.nabble.com/How-can-I-configure-a-different-sender-email-address-for-each-build-td4632260.html
In brief, put the following in pre-send script box.
import javax.mail.Message.RecipientType
import javax.mail.Address
import javax.mail.internet.InternetAddress
import javax.mail.internet.MimeMessage
msg.setFrom(new InternetAddress("email address"))
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18779) Jenkins slaves should have the ability to specify the FROM field
Bassam Khouri closed JENKINS-18779 as Wont Fix Jenkins slaves should have the ability to specify the FROM field Closing issue. Change By: Bassam Khouri (16/Jul/13 9:25 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [description-setter] (JENKINS-17461) Expose description as an environment variable.
Bassam Khouri commented on JENKINS-17461 Expose description as an environment variable. I would like the build description to be available as a token so I can use it in the email notification (i used email-ext) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18781) Configurable channel timeout for slaves
cowwoc created JENKINS-18781 Configurable channel timeout for slaves Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: core Created: 16/Jul/13 9:30 PM Description: This issue is related to JENKINS-6817. I am running Jenkins slaves inside virtual machines. Sometimes these machines are overloaded and I get the following exception: FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:713) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:167) at $Proxy38.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:925) at hudson.Launcher$ProcStarter.join(Launcher.java:360) at hudson.tasks.Maven.perform(Maven.java:327) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586) at hudson.model.Run.execute(Run.java:1593) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:247) Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:773) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:72) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Is it possible to make the channel timeout configurable? I'd like to increase the value from, say 5 seconds, to 30 seconds or a minute. Project: Jenkins Priority: Major Reporter: cowwoc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [conditional-buildstep] (JENKINS-18762) Build number environment variable is not propagated when run inside a conditional build step
Davi Arnaut commented on JENKINS-18762 Build number environment variable is not propagated when run inside a conditional build step One way to fix it is to add an optional dependency on conditional-buildstep. If it is present, it should be possible to upcast and get the list of builders. In the mean time, I'm just adding the action to every build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [master-slave] (JENKINS-18782) slave connection failed starting with 1.519
hlau created JENKINS-18782 slave connection failed starting with 1.519 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: master-slave Created: 16/Jul/13 10:41 PM Description: I tried this multiple times: slaves fail to connect when using version 1.519 or later; the same slaves connects fine when using 1.518 or earlier (as early as 1.501). The experiments were done with a simple jenkins with no jobs configured, and with only the master and a couple of slaves. Log shows the following error: ... 07/16/13 15:39:19 SSH Checking java version of java 07/16/13 15:39:19 SSH java -version returned 1.6.0_10. 07/16/13 15:39:19 SSH Starting sftp client. 07/16/13 15:39:19 SSH Copying latest slave.jar... 07/16/13 15:39:19 SSH Copied 326,006 bytes. Expanded the channel window size to 4MB 07/16/13 15:39:19 SSH Starting slave process: cd '/data00/hudson_home_analysis' java -jar slave.jar ===JENKINS REMOTING CAPACITY===channel started Slave.jar version: 2.24 This is a Unix slave hudson.util.IOException2: Failed to copy /jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.3.jar to /hudson_home/maven-agent.jar at hudson.FilePath.copyTo(FilePath.java:1726) at hudson.maven.MavenComputerListener.copyJar(MavenComputerListener.java:90) at hudson.maven.MavenComputerListener.preOnline(MavenComputerListener.java:57) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:469) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:343) at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:712) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:498) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:226) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: java.io.IOException: Remote call on repo-01 failed at hudson.remoting.Channel.call(Channel.java:731) at hudson.FilePath.write(FilePath.java:1625) at hudson.FilePath.copyTo(FilePath.java:1719) ... 12 more Caused by: java.lang.NoClassDefFoundError: org/apache/commons/io/input/ProxyInputStream at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:621) at java.lang.ClassLoader.defineClass(ClassLoader.java:466) at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:289) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:229) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) at java.lang.Class.getDeclaredFields0(Native Method) at java.lang.Class.privateGetDeclaredFields(Class.java:2291) at java.lang.Class.getDeclaredField(Class.java:1880) at java.io.ObjectStreamClass.getDeclaredSUID(ObjectStreamClass.java:1610) at java.io.ObjectStreamClass.access$700(ObjectStreamClass.java:52) at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:425) at java.security.AccessController.doPrivileged(Native Method) at java.io.ObjectStreamClass.init(ObjectStreamClass.java:413) at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:310) at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:547) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1583) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1732) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753) at
[JIRA] [master-slave] (JENKINS-18782) slave connection failed starting with 1.519
hlau commented on JENKINS-18782 slave connection failed starting with 1.519 A couple of things to note: slave.jar was successfully copied over to the slave yet maven-agent.jar failed to be copied over as indicated by the error. It does not look like a problem with ownership or permission or non-existence of the target directory (obviously since slave.jar was copied successfully). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-18783) Perforce plugin help file missing
robsimon created JENKINS-18783 Perforce plugin help file missing Issue Type: Bug Assignee: Rob Petti Components: perforce Created: 16/Jul/13 11:03 PM Description: Go within the job config to the Perforce settings. Click on the on the right-hand side for "Perforce Charset Options". Instead of a help text an error message "ERROR: Failed to load help file: Not Found" is displayed. Environment: perforce plugin v1.3.24, jenkins v1.5.17, Java jre1.7.0_17_64, Windows 7 Enterprise SP1 Project: Jenkins Priority: Major Reporter: robsimon This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18674) TypeError: registry is undefined in prototype.js:5621 when plot plugin publisher configuration reopened
Baba Buehler commented on JENKINS-18674 TypeError: registry is undefined in prototype.js:5621 when plot plugin publisher configuration reopened This issue is still present with 1.523 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plot] (JENKINS-18644) Loading Overlay
Baba Buehler commented on JENKINS-18644 Loading Overlay Issue is still present with Plot and 1.523 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [rake] (JENKINS-7530) Rake plugin fails when Job configured to use (Default) Rake installation.
Olivier Dagenais commented on JENKINS-7530 Rake plugin fails when Job configured to use (Default) Rake installation. John and Vikram: What version of Java is running on the machines where this happens? I think I narrowed a bug with the same repro steps as this one's title (and a similar work-around: specify a non-default Rake), but with a different root cause. I have reproduced when trying to launch the job on both a Windows master or a Windows slave, and I always get: [workspace] $ rake.bat '"C:\path\to\Jenkins\jobs\jobName\workspace\ruby.exe"' is not recognized as an internal or external command, operable program or batch file. Build step 'Invoke Rake' marked build as failure This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plot] (JENKINS-18644) Loading Overlay
Russell B commented on JENKINS-18644 Loading Overlay @Baba - I made this pull request last week that fixes the solution, albeit not in a way that addresses why plot plugin is causing a function to be called improperly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-18784) Easy way to pass a value from a build back to the flow
Jesse Glick
created JENKINS-18784
Easy way to pass a value from a build back to the flow
Issue Type:
Improvement
Assignee:
Nicolas De Loof
Components:
build-flow
Created:
16/Jul/13 11:57 PM
Description:
People often ask how you can pass a value from one build step to another in a Flow, or generally to retrieve information from builds. If you are willing to write the value to an archived file in the first build, you can use a function like
def artifact(build, name) {
new File(build.artifactsDir, name).text.trim();
}
This works, but the Flow plugin should define something like this (or better) out of the box.
(Also https://github.com/jenkinsci/jenkins/pull/736 would change the Jenkins API here, so it is better that the plugin take care of that detail.)
Project:
Jenkins
Priority:
Major
Reporter:
Jesse Glick
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: I/O error in channel CLI
I am having the same issue. Using SWARM plugin to manage slaves in matrix config project. the swarm jar will be executed at the time of windows startup. the slaves is up during the startup and able to run the job once, but afterwards the slave goes offline, Jenkins version is 1.523, I am stuck SEVERE: I/O error in channel machinename java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:189) at java.net.SocketInputStream.read(SocketInputStream.java:121) at java.io.BufferedInputStream.fill(BufferedInputStream.java:235) at java.io.BufferedInputStream.read(BufferedInputStream.java:254) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2266) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2559) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2569) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1315) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:72) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Jul 16, 2013 4:01:05 PM jenkins.slaves.JnlpSlaveAgentProtocol$Handler$1 onClosed WARNING: Channel reader thread: machinename for + machinename terminated java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:189) at java.net.SocketInputStream.read(SocketInputStream.java:121) at java.io.BufferedInputStream.fill(BufferedInputStream.java:235) at java.io.BufferedInputStream.read(BufferedInputStream.java:254) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2266) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2559) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2569) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1315) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:72) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) On Wednesday, March 30, 2011 9:48:02 PM UTC-7, Kohsuke Kawaguchi wrote: Note that the issues list is for automated notifications from the bug tracker. For questions like this, please use the users list. I suspect this is the remoting problem we fixed in 1.403. Which version do you run? On 03/30/2011 08:58 AM, khliang wrote: CLI-help command doesn't get a complete command list. And log shows I/O error in channel CLI. == D:\java -jar jenkins-cli.jar -s http://localhost:8080/ help build Builds a job, and optionally waits until its completion. cancel-quiet-down Cancel the effect of the quiet-down command. clear-queue Clears the build queue connect-node Reconnect to a node copy-job Copies a job create-job Creates a new job by reading stdin as a configuration XML file delete-builds Deletes build record(s) delete-job Deletes a job delete-node Deletes a node disable-job Disables a job disconnect-node D:\ == 2011/3/30 下午 11:51:07 hudson.remoting.Channel$ReaderThread run 嚴重的: I/O error in channel CLI channel from /127.0.0.1 java.net.SocketException: Connection reset at java.net.SocketInputStream.read(Unknown Source) at java.io.FilterInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at java.io.ObjectInputStream$PeekInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peek(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at hudson.remoting.Channel$ReaderThread.run(Channel.java:979) -- View this message in context: http://jenkins.361315.n4.nabble.com/I-O-error-in-channel-CLI-tp3418493p3418493.html Sent from the Jenkins issues mailing list archive at Nabble.com. -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-status] (JENKINS-18785) SWARM Plugin Slave connection reset issue
Kalps sat updated JENKINS-18785 SWARM Plugin Slave connection reset issue Change By: Kalps sat (17/Jul/13 12:12 AM) Fix Version/s: current This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
