[JIRA] (JENKINS-59062) Suppressed: java.lang.Throwable: HttpInput failure
Title: Message Title Dinesh updated an issue Jenkins / JENKINS-59062 Suppressed: java.lang.Throwable: HttpInput failure Change By: Dinesh I have my Jenkins with version 2.176.2, and I use cURL for automatically GET and POST Jenkins jobs. The automation was working before the Apache server update. Earlier it was using Apache server version - 2.4.39and it was upgraded to new version 2.4.41.I used cURL version 7.63. Through cURL I use API token for authentication. In Jenkins machine, under Access log of Apache software I get the issue as below:*"POST /view/All/job//configSubmit HTTP/1.1" 401 381*After the update of Apache server the build job updation through cURL was not working and it shows below issue in build job while posting := . Kindly provide inputs to resolve the issue.javax.xml.transform.TransformerException: java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms [exec] at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(Unknown Source) [exec] at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(Unknown Source) [exec] at jenkins.util.xml.XMLUtils._transform(XMLUtils.java:210) [exec] at jenkins.util.xml.XMLUtils.safeTransform(XMLUtils.java:82) [exec] at hudson.model.AbstractItem.updateByXml(AbstractItem.java:865) [exec] at hudson.model.AbstractItem.doConfigDotXml(AbstractItem.java:808) [exec] at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source) [exec] at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) [exec] at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) [exec] at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) [exec] at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) [exec] at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) [exec] at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) [exec] at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) [exec] at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) [exec] at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) [exec] at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) [exec] at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) [exec] at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) [exec] at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) [exec] at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) [exec] at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) [exec] at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) [exec] at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) [exec] at org.kohsuke.stapler.Stapler.service(Stapler.java:238) [exec] at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [exec] at org.eclipse.jetty.server.HttpInput$ErrorState.noContent(HttpInput.java:1085) [exec] at org.eclipse.jetty.server.HttpInput.read(HttpInput.java:318) [exec] at
[JIRA] (JENKINS-59062) Suppressed: java.lang.Throwable: HttpInput failure
Title: Message Title Dinesh updated an issue Jenkins / JENKINS-59062 Suppressed: java.lang.Throwable: HttpInput failure Change By: Dinesh I have my Jenkins with version 2.176.2, and I use cURL for automatically GET and POST Jenkins jobs. The automation was working before the Apache server update. Earlier it was using Apache server version - 2.4.39and it was upgraded to new version 2.4.41.I used cURL version 7.63. Through cURL I use API token for authentication. In Jenkins machine, under Access log of Apache software I get the issue as below:*"POST /view/All/job//configSubmit HTTP/1.1" 401 381*After the update of Apache server the build job updation through cURL was not working and it shows below issue in build job while posting: =. Kindly provide inputs to resolve the issue. javax.xml.transform.TransformerException: java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms[exec] at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(Unknown Source)[exec] at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(Unknown Source)[exec] at jenkins.util.xml.XMLUtils._transform(XMLUtils.java:210)[exec] at jenkins.util.xml.XMLUtils.safeTransform(XMLUtils.java:82)[exec] at hudson.model.AbstractItem.updateByXml(AbstractItem.java:865)[exec] at hudson.model.AbstractItem.doConfigDotXml(AbstractItem.java:808)[exec] at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source)[exec] at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)[exec] at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408)[exec] at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212)[exec] at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145)[exec] at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535)[exec] at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)[exec] at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)[exec] at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878)[exec] at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280)[exec] at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)[exec] at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)[exec] at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878)[exec] at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280)[exec] at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)[exec] at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)[exec] at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878)[exec] at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676)[exec] at org.kohsuke.stapler.Stapler.service(Stapler.java:238)[exec] at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)[exec] at org.eclipse.jetty.server.HttpInput$ErrorState.noContent(HttpInput.java:1085)[exec] at org.eclipse.jetty.server.HttpInput.read(HttpInput.java:318)[exec] at sun.nio.cs.StreamDecoder.readBytes(Unknown
[JIRA] (JENKINS-59062) Suppressed: java.lang.Throwable: HttpInput failure
Title: Message Title Dinesh created an issue Jenkins / JENKINS-59062 Suppressed: java.lang.Throwable: HttpInput failure Issue Type: Bug Assignee: Armando Fernandez Components: ant-plugin, apache-httpcomponents-client-4-api-plugin Created: 2019-08-23 06:07 Environment: Jenkins version - 2.176.2 Apache server version - 2.4.39 (Old version) 2.4.41 (New version) Priority: Major Reporter: Dinesh I have my Jenkins with version 2.176.2, and I use cURL for automatically GET and POST Jenkins jobs. The automation was working before the Apache server update. Earlier it was using Apache server version - 2.4.39and it was upgraded to new version 2.4.41. I used cURL version 7.63. Through cURL I use API token for authentication. In Jenkins machine, under Access log of Apache software I get the issue as below: "POST /view/All/job//configSubmit HTTP/1.1" 401 381 After the update of Apache server the build job updation through cURL was not working and it shows below issue in build job while posting: javax.xml.transform.TransformerException: java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms [exec] at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(Unknown Source) [exec] at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(Unknown Source) [exec] at jenkins.util.xml.XMLUtils._transform(XMLUtils.java:210) [exec] at jenkins.util.xml.XMLUtils.safeTransform(XMLUtils.java:82) [exec] at hudson.model.AbstractItem.updateByXml(AbstractItem.java:865) [exec] at hudson.model.AbstractItem.doConfigDotXml(AbstractItem.java:808) [exec] at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source) [exec] at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) [exec] at
[JIRA] (JENKINS-53893) org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method hudson.model.Item getName
Title: Message Title Dinesh updated an issue Jenkins / JENKINS-53893 org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method hudson.model.Item getName Change By: Dinesh I was trying to archive the old jenkins builds using a groovy script, and earlier it was working fine and without any changes now I am facing issue as below:ERROR: Build step failed with exception org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method hudson.model.Item getName at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectMethod(StaticWhitelist.java:175) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:137) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:155) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:159) at org.kohsuke.groovy.sandbox.impl.Checker$checkedCall.callStatic(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:56) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:194) at Script1.deleteBuildHistory(Script1.groovy:71) at Script1$deleteBuildHistory.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:157) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:133) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:155) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:159) at org.kohsuke.groovy.sandbox.impl.Checker$checkedCall.callStatic(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:56) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:194) at Script1.run(Script1.groovy:58) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.run(GroovySandbox.java:141) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SecureGroovyScript.evaluate(SecureGroovyScript.java:333) at hudson.plugins.groovy.SystemGroovy.run(SystemGroovy.java:95) at hudson.plugins.groovy.SystemGroovy.perform(SystemGroovy.java:59) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1798) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at
[JIRA] (JENKINS-53893) org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method hudson.model.Item getName
Title: Message Title Dinesh created an issue Jenkins / JENKINS-53893 org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method hudson.model.Item getName Issue Type: Bug Assignee: vjuranek Components: groovy-plugin Created: 2018-10-04 05:52 Environment: My Jenkins version - 2.121.2 Priority: Critical Reporter: Dinesh I was trying to archive the old jenkins builds using a groovy script, and earlier it was working fine and without any changes now I am facing issue as below: ERROR: Build step failed with exception org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method hudson.model.Item getName at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectMethod(StaticWhitelist.java:175) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:137) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:155) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:159) at org.kohsuke.groovy.sandbox.impl.Checker$checkedCall.callStatic(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:56) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:194) at Script1.deleteBuildHistory(Script1.groovy:71) at Script1$deleteBuildHistory.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:157) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23) at
[JIRA] (JENKINS-53435) Categorizing of jenkins job failing
Title: Message Title Dinesh updated an issue Jenkins / JENKINS-53435 Categorizing of jenkins job failing Change By: Dinesh I wanted to add my Jenkins job into a particular category in view, we used *jenkins-cli.jar* for this (This is an automation). It was working earlier and since few weeks it stopped working and facing the below issue. [java] Exception in thread "main" java.io.EOFException [java] at java.io.DataInputStream.readFully(DataInputStream.java:197) [java] at java.io.DataInputStream.readUTF(DataInputStream.java:609) [java] at java.io.DataInputStream.readUTF(DataInputStream.java:564) [java] at hudson.cli.CLI.connectViaCliPort(CLI.java:225) [java] at hudson.cli.CLI.(CLI.java:126) [java] at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72) [java] at hudson.cli.CLI._main(CLI.java:466) [java] at hudson.cli.CLI.main(CLI.java:382) [java] Suppressed: java.io.EOFException: unexpected stream termination [java] at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:331) [java] at hudson.remoting.Channel.(Channel.java:421) [java] at hudson.remoting.Channel.(Channel.java:400) [java] at hudson.remoting.Channel.(Channel.java:396) [java] at hudson.remoting.Channel.(Channel.java:385) [java] at hudson.remoting.Channel.(Channel.java:377) [java] at hudson.remoting.Channel.(Channel.java:353) [java] at hudson.cli.CLI.connectViaHttp(CLI.java:157) [java] at hudson.cli.CLI.(CLI.java:130) [java] ... 3 more The only change made in project was the URL from HTTP to HTTPS. Will it cause the issue to happen ? If this is the issue * how can we to make it jenkins-cli.jar to work for HTTPS* ? Please suggest.As an alternative way, I tried creating Jenkins job inside a view using cURL and I wanted the particular job inside a category. Moving a job inside category doesn't work here. Kindly help. Add Comment
[JIRA] (JENKINS-53435) Categorizing of jenkins job failing
Title: Message Title Dinesh updated an issue Jenkins / JENKINS-53435 Categorizing of jenkins job failing Change By: Dinesh I wanted to move add my Jenkins job into a particular category in view, we used *jenkins-cli.jar* for this (This is an automation). It was working earlier and since few weeks it stopped working and facing the below issue. [java] Exception in thread "main" java.io.EOFException [java] at java.io.DataInputStream.readFully(DataInputStream.java:197) [java] at java.io.DataInputStream.readUTF(DataInputStream.java:609) [java] at java.io.DataInputStream.readUTF(DataInputStream.java:564) [java] at hudson.cli.CLI.connectViaCliPort(CLI.java:225) [java] at hudson.cli.CLI.(CLI.java:126) [java] at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72) [java] at hudson.cli.CLI._main(CLI.java:466) [java] at hudson.cli.CLI.main(CLI.java:382) [java] Suppressed: java.io.EOFException: unexpected stream termination [java] at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:331) [java] at hudson.remoting.Channel.(Channel.java:421) [java] at hudson.remoting.Channel.(Channel.java:400) [java] at hudson.remoting.Channel.(Channel.java:396) [java] at hudson.remoting.Channel.(Channel.java:385) [java] at hudson.remoting.Channel.(Channel.java:377) [java] at hudson.remoting.Channel.(Channel.java:353) [java] at hudson.cli.CLI.connectViaHttp(CLI.java:157) [java] at hudson.cli.CLI.(CLI.java:130) [java] ... 3 more The only change made in project was the URL from HTTP to HTTPS. Will it cause the issue to happen ? If this is the issue how can we make it work ? Please suggest.As an alternative way, I tried creating Jenkins job inside a view using cURL and I wanted the particular job inside a category. Moving a job inside category doesn't work here. Kindly help. Add Comment
[JIRA] (JENKINS-53435) Categorizing of jenkins job failing
Title: Message Title Dinesh assigned an issue to KaiHsiang Chang Jenkins / JENKINS-53435 Categorizing of jenkins job failing Change By: Dinesh Assignee: KaiHsiang Chang Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53435) Categorizing of jenkins job failing
Title: Message Title Dinesh updated an issue Jenkins / JENKINS-53435 Categorizing of jenkins job failing Change By: Dinesh I wanted to move my Jenkins job into a particular category in view, we used *jenkins-cli.jar* for this (This is an automation). It was working earlier and since few weeks it stopped working and facing the below issue. [java] Exception in thread "main" java.io.EOFException [java] at java.io.DataInputStream.readFully(DataInputStream.java:197) [java] at java.io.DataInputStream.readUTF(DataInputStream.java:609) [java] at java.io.DataInputStream.readUTF(DataInputStream.java:564) [java] at hudson.cli.CLI.connectViaCliPort(CLI.java:225) [java] at hudson.cli.CLI.(CLI.java:126) [java] at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72) [java] at hudson.cli.CLI._main(CLI.java:466) [java] at hudson.cli.CLI.main(CLI.java:382) [java] Suppressed: java.io.EOFException: unexpected stream termination [java] at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:331) [java] at hudson.remoting.Channel.(Channel.java:421) [java] at hudson.remoting.Channel.(Channel.java:400) [java] at hudson.remoting.Channel.(Channel.java:396) [java] at hudson.remoting.Channel.(Channel.java:385) [java] at hudson.remoting.Channel.(Channel.java:377) [java] at hudson.remoting.Channel.(Channel.java:353) [java] at hudson.cli.CLI.connectViaHttp(CLI.java:157) [java] at hudson.cli.CLI.(CLI.java:130) [java] ... 3 more The only change made in project was the URL from HTTP to HTTPS. Will it cause the issue to happen ? If this is the issue how can we make it work ? Please suggest. As an alternative way, I tried creating Jenkins job inside a view using cURL and I wanted the particular job inside a category. Moving a job inside category doesn't work here. Kindly help. Add Comment
[JIRA] (JENKINS-53435) Categorizing of jenkins job failing
Title: Message Title Dinesh created an issue Jenkins / JENKINS-53435 Categorizing of jenkins job failing Issue Type: Bug Assignee: Unassigned Components: cli Created: 2018-09-06 05:28 Environment: Jenkins version - 2.121.2 Priority: Critical Reporter: Dinesh I wanted to move my Jenkins job into a particular category in view, we used jenkins-cli.jar for this (This is an automation). It was working earlier and since few weeks it stopped working and facing the below issue. [java] Exception in thread "main" java.io.EOFException [java] at java.io.DataInputStream.readFully(DataInputStream.java:197) [java] at java.io.DataInputStream.readUTF(DataInputStream.java:609) [java] at java.io.DataInputStream.readUTF(DataInputStream.java:564) [java] at hudson.cli.CLI.connectViaCliPort(CLI.java:225) [java] at hudson.cli.CLI.(CLI.java:126) [java] at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72) [java] at hudson.cli.CLI._main(CLI.java:466) [java] at hudson.cli.CLI.main(CLI.java:382) [java] Suppressed: java.io.EOFException: unexpected stream termination [java] at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:331) [java] at hudson.remoting.Channel.(Channel.java:421) [java] at hudson.remoting.Channel.(Channel.java:400) [java] at hudson.remoting.Channel.(Channel.java:396) [java] at hudson.remoting.Channel.(Channel.java:385) [java] at hudson.remoting.Channel.(Channel.java:377) [java] at hudson.remoting.Channel.(Channel.java:353) [java] at hudson.cli.CLI.connectViaHttp(CLI.java:157) [java] at hudson.cli.CLI.(CLI.java:130) [java] ... 3 more The only change made in project was the URL from HTTP to HTTPS. Will it cause the issue to happen ? If this is the issue how can we make it work ? Please suggest. As an alternative way, I tried creating Jenkins
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title Dinesh commented on JENKINS-52810 Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins The issue got resolved when the parameter "Block until the remote triggered projects finish their builds" is set to false (Uncheck the check box). The build is green now. Thank you for the support provided KaiHsiang Chang. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title Dinesh edited a comment on JENKINS-52810 Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins [~cashlalala], Still I have validated the configurations comparing with yours, and now the build is not failing. Now I am facing issue as below, and the build is not ending and still it tried to run the 1st build job in the folder again and again, and it is not trying to execute the 2nd and next build jobs in the folder: Can you please try to trigger more than 1 job in a particular folder and update whether it is triggering all of them. Parameterized Remote Trigger Configuration: - job: // - remoteJenkinsName: Jenkins Server - parameters: [Version1=test22, Version2=test21] - blockBuildUntilComplete: false - connectionRetryLimit: 5fail to accquire lock because of timeout, skip locking...Triggering parameterized remote job 'http:///job/' Using globally defined 'Credentials Authentication' as user 'username' (Credentials ID 'my credentials id')Triggering remote job now.fail to accquire lock because of timeout, skip locking...CSRF protection is disabled on the remote server.fail to accquire lock because of timeout, skip locking...The remote job is blocked. Build #58 is already in progress (ETA:34 min). Remote job queue number: 101142Waiting for remote build to be executed...Waiting for 10 seconds until next poll.fail to accquire lock because of timeout, skip locking...The remote job is blocked. Build #58 is already in progress (ETA:33 min).Waiting for 10 seconds until next poll.fail to accquire lock because of timeout, skip locking...The remote job is blocked. Build #58 is already in progress (ETA:33 min).Waiting for 10 seconds until next poll.fail to accquire lock because of timeout, skip locking...The remote job is blocked. Build #58 is already in progress (ETA:33 min).Waiting for 10 seconds until next poll.fail to accquire lock because of timeout, skip locking...The remote job is blocked. Build #58 is already in progress (ETA:32 min).Waiting for 10 seconds until next poll.fail to accquire lock because of timeout, skip locking...The remote job is blocked. Build #58 is already in progress (ETA:32 min).Waiting for 10 seconds until next poll.fail to accquire lock because of timeout, skip locking...The remote job is blocked. Build #58 is already in progress (ETA:32 min).Waiting for 10 seconds until next poll.fail to accquire lock because of timeout, skip locking...The remote job is blocked. Build #58 is already in progress (ETA:31 min).Waiting for 10 seconds until next poll.fail to accquire lock because of timeout, skip locking... Add Comment
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title Dinesh commented on JENKINS-52810 Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins KaiHsiang Chang, Still I have validated the configurations comparing with yours, and now the build is not failing. Now I am facing issue as below, and the build is not ending and still it tried to run the 1st build job in the folder again and again, and it is not trying to execute the 2nd and next build jobs in the folder: Parameterized Remote Trigger Configuration: job: // remoteJenkinsName: Jenkins Server parameters: [Version1=test22, Version2=test21] blockBuildUntilComplete: false connectionRetryLimit: 5 fail to accquire lock because of timeout, skip locking... Triggering parameterized remote job 'http:///job/' Using globally defined 'Credentials Authentication' as user 'username' (Credentials ID 'my credentials id') Triggering remote job now. fail to accquire lock because of timeout, skip locking... CSRF protection is disabled on the remote server. fail to accquire lock because of timeout, skip locking... The remote job is blocked. Build #58 is already in progress (ETA:34 min). Remote job queue number: 101142 Waiting for remote build to be executed... Waiting for 10 seconds until next poll. fail to accquire lock because of timeout, skip locking... The remote job is blocked. Build #58 is already in progress (ETA:33 min). Waiting for 10 seconds until next poll. fail to accquire lock because of timeout, skip locking... The remote job is blocked. Build #58 is already in progress (ETA:33 min). Waiting for 10 seconds until next poll. fail to accquire lock because of timeout, skip locking... The remote job is blocked. Build #58 is already in progress (ETA:33 min). Waiting for 10 seconds until next poll. fail to accquire lock because of timeout, skip locking... The remote job is blocked. Build #58 is already in progress (ETA:32 min). Waiting for 10 seconds until next poll. fail to accquire lock because of timeout, skip locking... The remote job is blocked. Build #58 is already in progress (ETA:32 min). Waiting for 10 seconds until next poll. fail to accquire lock because of timeout, skip locking... The remote job is blocked. Build #58 is already in progress (ETA:32 min). Waiting for 10 seconds until next poll. fail to accquire lock because of timeout, skip locking... The remote job is blocked. Build #58 is already in progress (ETA:31 min). Waiting for 10 seconds until next poll. fail to accquire lock because of timeout, skip locking...
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title Dinesh commented on JENKINS-52810 Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins Can you please share your both jenkins configurations for reference, so that i will still validate accordingly. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title Dinesh edited a comment on JENKINS-52810 Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins Both the URL's are identical only, since i have blurred it was looking like a different URL. In the remote server failing part in log (json appending URL), the URL is coming till which i have mentioned in the jenkins A configuration only. The remaining URL which i am giving in my job is not reflecting in the URL (Folder name and job name is not appending with the URL). Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title Dinesh commented on JENKINS-52810 Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins Both the URL's are identical only, since i have blurred it was looking like a different URL. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title Dinesh commented on JENKINS-52810 Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins I have updated the configurations according to what you have suggested, and we face the issue as attached. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title Dinesh updated an issue Jenkins / JENKINS-52810 Parameterized Remote Trigger Plugin is not triggering job in remote jenkins Change By: Dinesh Attachment: RemoteTriggerFailure.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title Dinesh commented on JENKINS-52810 Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins In the folder, out of number of jobs it is triggering only the 1st job and failing with the same issue. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title Dinesh commented on JENKINS-52810 Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins Please find my remote server configuration attached: (As I have already mentioned, I wanted to trigger some 5 jobs inside folder, i wanted to provide my folder name in the URL) Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title Dinesh updated an issue Jenkins / JENKINS-52810 Parameterized Remote Trigger Plugin is not triggering job in remote jenkins Change By: Dinesh Attachment: TimeOutRemoteTrigger.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title Dinesh commented on JENKINS-52810 Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins I agree with your point, but in the URL at last it is appending queue/item//api/json and now that is the place where the issue is with, and we are not pretty sure from where this is getting appended. Even after providing the URL with the same format provided by you, still the same issue exists with the URL and it shows: Connection to remote server failed [404], waiting for to retry - 10 seconds until next attempt. URL: https:queue/item/81594/api/json/, parameters: Retry attempt #5 out of 5 ERROR: Remote build failed with 'ExceedRetryLimitException' for the following reason: 'Max number of connection retries have been exeeded.'. ERROR: ExceedRetryLimitException: Max number of connection retries have been exeeded. Finished: FAILURE Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title Dinesh commented on JENKINS-52810 Re: Parameterized Remote Trigger Plugin is not triggering job in remote jenkins I have validated the configurations and all are proper. When i executed the build i am facing the below issue without a configuration change : fail to accquire lock because of timeout, skip locking... CSRF protection is disabled on the remote server. fail to accquire lock because of timeout, skip locking... Connection to remote server failed [404], waiting for to retry - 10 seconds until next attempt. URL: https:///view/All/queue/item/81305/api/json/, parameters: Retry attempt #1 out of 5 Connection to remote server failed [404], waiting for to retry - 10 seconds until next attempt. URL: https:///view/All/queue/item/81305/api/json/ parameters: Retry attempt #2 out of 5 Connection to remote server failed [404], waiting for to retry - 10 seconds until next attempt. URL: https:///view/All/queue/item/81305/api/json/, parameters: Retry attempt #3 out of 5 Connection to remote server failed [404], waiting for to retry - 10 seconds until next attempt. URL: https:///view/All/queue/item/81305/api/json/, parameters: Retry attempt #4 out of 5 Connection to remote server failed [404], waiting for to retry - 10 seconds until next attempt. URL: https:///view/All/queue/item/81305/api/json/, parameters: Retry attempt #5 out of 5 ERROR: Remote build failed with 'ExceedRetryLimitException' for the following reason: 'Max number of connection retries have been exeeded.'. ERROR: ExceedRetryLimitException: Max number of connection retries have been exeeded. BTW, in the error "view/All/queue/item/81305/api/json/" is automatically getting added. If that is added in URL the same path will not be present. Kindly can you provide your inputs. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send
