[JIRA] (JENKINS-57004) Error with jira plugin: Request cannot be executed; I/O reactor status: STOPPED
Title: Message Title
Alexey Grigorov edited a comment on JENKINS-57004
Re: Error with jira plugin: Request cannot be executed; I/O reactor status: STOPPED
3.0.10 similar error ``` {noformat} java.lang.IllegalStateException: Request cannot be executed; I/O reactor status: STOPPED at org.apache.http.util.Asserts.check(Asserts.java:46) at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase.ensureRunning(CloseableHttpAsyncClientBase.java:90) at org.apache.http.impl.nio.client.InternalHttpAsyncClient.execute(InternalHttpAsyncClient.java:123) at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:75) at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:108) at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient.execute(SettableFuturePromiseHttpPromiseAsyncClient.java:36) at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.doExecute(ApacheAsyncHttpClient.java:417) at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.execute(ApacheAsyncHttpClient.java:364) at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest$DefaultRequestBuilder.execute(DefaultRequest.java:297) at com.atlassian.jira.rest.client.internal.async.AtlassianHttpClientDecorator$AuthenticatedRequestBuilder.execute(AtlassianHttpClientDecorator.java:83) at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest$DefaultRequestBuilder.get(DefaultRequest.java:253) at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient.getAndParse(AbstractAsynchronousRestClient.java:69) at com.atlassian.jira.rest.client.internal.async.AsynchronousProjectRestClient.getProject(AsynchronousProjectRestClient.java:50) ``` {noformat}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-57004) Error with jira plugin: Request cannot be executed; I/O reactor status: STOPPED
Title: Message Title Alexey Grigorov commented on JENKINS-57004 Re: Error with jira plugin: Request cannot be executed; I/O reactor status: STOPPED 3.0.10 similar error ``` java.lang.IllegalStateException: Request cannot be executed; I/O reactor status: STOPPED at org.apache.http.util.Asserts.check(Asserts.java:46) at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase.ensureRunning(CloseableHttpAsyncClientBase.java:90) at org.apache.http.impl.nio.client.InternalHttpAsyncClient.execute(InternalHttpAsyncClient.java:123) at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:75) at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:108) at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient.execute(SettableFuturePromiseHttpPromiseAsyncClient.java:36) at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.doExecute(ApacheAsyncHttpClient.java:417) at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.execute(ApacheAsyncHttpClient.java:364) at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest$DefaultRequestBuilder.execute(DefaultRequest.java:297) at com.atlassian.jira.rest.client.internal.async.AtlassianHttpClientDecorator$AuthenticatedRequestBuilder.execute(AtlassianHttpClientDecorator.java:83) at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest$DefaultRequestBuilder.get(DefaultRequest.java:253) at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient.getAndParse(AbstractAsynchronousRestClient.java:69) at com.atlassian.jira.rest.client.internal.async.AsynchronousProjectRestClient.getProject(AsynchronousProjectRestClient.java:50) ``` Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-54121) Renaming jobs casue Jenkins crash
Title: Message Title
Alexey Grigorov edited a comment on JENKINS-54121
Re: Renaming jobs casue Jenkins crash
Hi [~danielbeck]I have same issue, jenkins 2.176.1, user tried to rename a folder containing 2 millions filesjenkins heap of 31 Gb become full and jenkins died in gc trace is { noformat code:java }"Handling POST /job/Avolin/job/Tradebeam/job/GTM-2/confirmRename from 10.212.255.245 : qtp1254526270-61611" #61611 prio=5 os_prio=0 tid=0x7f60801c6800 nid=0x3ee0 runnable [0x7f601d863000]"Handling POST /job/Avolin/job/Tradebeam/job/GTM-2/confirmRename from 10.212.255.245 : qtp1254526270-61611" #61611 prio=5 os_prio=0 tid=0x7f60801c6800 nid=0x3ee0 runnable [0x7f601d863000] java.lang.Thread.State: RUNNABLE at java.util.HashMap.putVal(HashMap.java:631) at java.util.HashMap.put(HashMap.java:612) at org.apache.tools.ant.util.LinkedHashtable.put(LinkedHashtable.java:110) - locked <0x7f624dfde3e0> (a org.apache.tools.ant.util.LinkedHashtable) at org.apache.tools.ant.taskdefs.Copy.buildMap(Copy.java:788) at org.apache.tools.ant.taskdefs.Copy.scan(Copy.java:735) at org.apache.tools.ant.taskdefs.Copy.iterateOverBaseDirs(Copy.java:660) at org.apache.tools.ant.taskdefs.Copy.execute(Copy.java:559) at hudson.model.AbstractItem.renameTo(AbstractItem.java:423) - locked <0x7f621d7a18f8> (a com.cloudbees.hudson.plugins.folder.Folder) - locked <0x7f6216b530b0> (a com.cloudbees.hudson.plugins.folder.Folder) at com.cloudbees.hudson.plugins.folder.AbstractFolder.renameTo(AbstractFolder.java:1305) at hudson.model.AbstractItem.doConfirmRename(AbstractItem.java:264) at java.lang.invoke.LambdaForm$DMH/769287236.invokeVirtual_LL_L(LambdaForm$DMH) at java.lang.invoke.LambdaForm$BMH/1605795346.reinvoke(LambdaForm$BMH) at java.lang.invoke.LambdaForm$MH/21979174.invoker(LambdaForm$MH) at java.lang.invoke.LambdaForm$MH/29329.invokeExact_MT(LambdaForm$MH) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) { noformat code }here is a shot from MAT , report archive attached!image-2019-07-18-22-42-26-771.png!
Add Comment
[JIRA] (JENKINS-54121) Renaming jobs casue Jenkins crash
Title: Message Title Alexey Grigorov commented on JENKINS-54121 Re: Renaming jobs casue Jenkins crash Hi Daniel Beck I have same issue, jenkins 2.176.1, user tried to rename a folder containing 2 millions files jenkins heap of 31 Gb become full and jenkins died in gc trace is "Handling POST /job/Avolin/job/Tradebeam/job/GTM-2/confirmRename from 10.212.255.245 : qtp1254526270-61611" #61611 prio=5 os_prio=0 tid=0x7f60801c6800 nid=0x3ee0 runnable [0x7f601d863000]"Handling POST /job/Avolin/job/Tradebeam/job/GTM-2/confirmRename from 10.212.255.245 : qtp1254526270-61611" #61611 prio=5 os_prio=0 tid=0x7f60801c6800 nid=0x3ee0 runnable [0x7f601d863000] java.lang.Thread.State: RUNNABLE at java.util.HashMap.putVal(HashMap.java:631) at java.util.HashMap.put(HashMap.java:612) at org.apache.tools.ant.util.LinkedHashtable.put(LinkedHashtable.java:110) - locked <0x7f624dfde3e0> (a org.apache.tools.ant.util.LinkedHashtable) at org.apache.tools.ant.taskdefs.Copy.buildMap(Copy.java:788) at org.apache.tools.ant.taskdefs.Copy.scan(Copy.java:735) at org.apache.tools.ant.taskdefs.Copy.iterateOverBaseDirs(Copy.java:660) at org.apache.tools.ant.taskdefs.Copy.execute(Copy.java:559) at hudson.model.AbstractItem.renameTo(AbstractItem.java:423) - locked <0x7f621d7a18f8> (a com.cloudbees.hudson.plugins.folder.Folder) - locked <0x7f6216b530b0> (a com.cloudbees.hudson.plugins.folder.Folder) at com.cloudbees.hudson.plugins.folder.AbstractFolder.renameTo(AbstractFolder.java:1305) at hudson.model.AbstractItem.doConfirmRename(AbstractItem.java:264) at java.lang.invoke.LambdaForm$DMH/769287236.invokeVirtual_LL_L(LambdaForm$DMH) at java.lang.invoke.LambdaForm$BMH/1605795346.reinvoke(LambdaForm$BMH) at java.lang.invoke.LambdaForm$MH/21979174.invoker(LambdaForm$MH) at java.lang.invoke.LambdaForm$MH/29329.invokeExact_MT(LambdaForm$MH) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) here is a shot from MAT , report archive attached
[JIRA] (JENKINS-54121) Renaming jobs casue Jenkins crash
Title: Message Title Alexey Grigorov reopened an issue Jenkins / JENKINS-54121 Renaming jobs casue Jenkins crash Change By: Alexey Grigorov Resolution: Incomplete Status: Closed Reopened 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194748.1539771324000.15730.1563479280346%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54121) Renaming jobs casue Jenkins crash
Title: Message Title Alexey Grigorov updated an issue Jenkins / JENKINS-54121 Renaming jobs casue Jenkins crash Change By: Alexey Grigorov Attachment: heapdump07-18-19_12_36_Leak_Suspects.zip 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194748.1539771324000.15724.1563479160169%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54121) Renaming jobs casue Jenkins crash
Title: Message Title Alexey Grigorov updated an issue Jenkins / JENKINS-54121 Renaming jobs casue Jenkins crash Change By: Alexey Grigorov Attachment: image-2019-07-18-22-42-26-771.png 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194748.1539771324000.15721.1563478980205%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58020) agent connected via TCP but executor does not show up online sometimes
Title: Message Title Alexey Grigorov updated an issue Jenkins / JENKINS-58020 agent connected via TCP but executor does not show up online sometimes Change By: Alexey Grigorov Environment: Jenkins 2. 164 176 . 3 1 , Remoting 3.29 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200041.1560527687000.11674.1561724520187%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58020) agent connected via TCP but executor does not show up online sometimes
Title: Message Title
Alexey Grigorov updated an issue
Jenkins / JENKINS-58020
agent connected via TCP but executor does not show up online sometimes
Change By:
Alexey Grigorov
Hi Jenkins team/communitywe started to observe that our cloud agents sometimes (roughly fail rate is - 10% - 0.5% of launches) fail to come up online within first attempt. Here it a timeline and logs of such case:~13:40 agent was created by cloud plugin (VMware in this case, but same problem was observed on kubernetes cloud also, so i suggest cloud type is not important)Here is agent log{noformat}Jun 14, 2019 1:40:29 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDirINFO: Using c:\remoting as a remoting work directoryJun 14, 2019 1:40:30 PM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: dev-take-onescm-build__1Jun 14, 2019 1:40:30 PM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode.Jun 14, 2019 1:40:30 PM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.29Jun 14, 2019 1:40:30 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDirINFO: Using c:\remoting as a remoting work directoryJun 14, 2019 1:40:30 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among [http://jenkins.aureacentral.com/]Jun 14, 2019 1:40:30 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Jun 14, 2019 1:40:30 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful Agent address: jenkins.aureacentral.com Agent port:5 Identity: a6:78:37:21:42:8e:c2:e1:08:e2:45:8b:83:df:c2:46Jun 14, 2019 1:40:30 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingJun 14, 2019 1:40:30 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to jenkins.aureacentral.com:5Jun 14, 2019 1:40:30 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectJun 14, 2019 1:40:31 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: a6:78:37:21:42:8e:c2:e1:08:e2:45:8b:83:df:c2:46Jun 14, 2019 1:40:32 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connected{noformat}here is part of server log related to same agent{noformat}Jun 14, 2019 1:40:36 PM org.jenkinsci.plugins.vSphereCloud InternalLogINFO: [dev-take-onescm-build__1] Slave has come online.Jun 14, 2019 1:40:36 PM org.jenkinsci.plugins.vSphereCloud InternalLogINFO: [dev-take-onescm-build__1] Slave onlineJun 14, 2019 1:40:37 PM org.jenkinsci.plugins.vSphereCloud$VSpherePlannedNode$1 callINFO: Provisioned new slave dev-take-onescm-build__1Jun 14, 2019 1:41:17 PM hudson.slaves.NodeProvisioner$2 runINFO: dev-take-onescm-build__1 provisioning successfully completed. We have now 674 computer(s){noformat}but agent did not show up online at 13:40 as you can see on load statistic screenshot (0 executors available) !image-2019-06-14-18-48-15-448.png|width=518,height=404!I waited 5 minutes and restarted jenkins
[JIRA] (JENKINS-58020) agent connected via TCP but executor does not show up online sometimes
Title: Message Title Alexey Grigorov commented on JENKINS-58020 Re: agent connected via TCP but executor does not show up online sometimes seems in my initial post I overestimated fail rate, according to last logs I have on kubernetes fail rate is just 0.5% 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200041.1560527687000.11664.1561723740091%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58020) agent connected via TCP but executor does not show up online sometimes
Title: Message Title Alexey Grigorov commented on JENKINS-58020 Re: agent connected via TCP but executor does not show up online sometimes Last week we upgraded to 2.176.1 LTS, problem still happening here is example on k8s this time on 10:06 agent log says it is connected but server waits for 15 minutes it until timeout exceeded and than kill container java.lang.IllegalStateException: Agent is not connected after 900 seconds, status: Running at org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher.launch(KubernetesLauncher.java:193) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) 2019-06-28 10:21:55.279+ [id=13265377] FINER o.c.j.p.k.KubernetesLauncher#launch: Removing Jenkins node: northplains-xinet-centos6-cibuild-dmz04 here https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesLauncher.java#L185 slaveComputer == null || slaveComputer.isOffline() condition is true 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
[JIRA] (JENKINS-58020) agent connected via TCP but executor does not show up online sometimes
Title: Message Title Alexey Grigorov updated an issue Jenkins / JENKINS-58020 agent connected via TCP but executor does not show up online sometimes Change By: Alexey Grigorov Attachment: image-2019-06-28-14-54-50-188.png 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200041.1560527687000.11637.1561722900258%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58020) agent connected via TCP but executor does not show up online sometimes
Title: Message Title Alexey Grigorov created an issue Jenkins / JENKINS-58020 agent connected via TCP but executor does not show up online sometimes Issue Type: Bug Assignee: Jeff Thompson Attachments: image-2019-06-14-18-48-15-448.png Components: core, remoting Created: 2019-06-14 15:54 Environment: Jenkins 2.164.3 , Remoting 3.29 Priority: Critical Reporter: Alexey Grigorov Hi Jenkins team/community we started to observe that our cloud agents sometimes (roughly fail rate is 10% of launches) fail to come up online within first attempt. Here it a timeline and logs of such case: ~13:40 agent was created by cloud plugin (VMware in this case, but same problem was observed on kubernetes cloud also, so i suggest cloud type is not important) Here is agent log Jun 14, 2019 1:40:29 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using c:\remoting as a remoting work directory Jun 14, 2019 1:40:30 PM hudson.remoting.jnlp.Main createEngine INFO: Setting up agent: dev-take-onescm-build__1 Jun 14, 2019 1:40:30 PM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode. Jun 14, 2019 1:40:30 PM hudson.remoting.Engine startEngine INFO: Using Remoting version: 3.29 Jun 14, 2019 1:40:30 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using c:\remoting as a remoting work directory Jun 14, 2019 1:40:30 PM
[JIRA] (JENKINS-57874) parametrized scheduler misfire job executions
Title: Message Title Alexey Grigorov created an issue Jenkins / JENKINS-57874 parametrized scheduler misfire job executions Issue Type: Bug Assignee: Baptiste Mathus Components: parameterized-scheduler-plugin Created: 2019-06-06 09:05 Environment: Parameterized Scheduler 0.6.3 jenkins 1.164.3 openjdk8, ubuntu 16.04 Priority: Critical Reporter: Alexey Grigorov Hi we have jobs scheduled via parametrized scheduler not started sometimes 2019-06-06 07:36:06.705+ [id=77]FINEo.j.p.p.Cron#checkTriggers: cron checking somejob1 2019-06-06 07:36:06.706+ [id=77]FINEo.j.p.p.ParameterizedTimerTrigger#checkCronTabsAndRun: checking and maybe running at java.util.GregorianCalendar[time=1559806566705,areFieldsSet=true,areAllFieldsSet=true,lenient=true,zone=sun.util.calendar.ZoneInfo[id="Etc/UTC",offset=0,dstSavings=0,useDaylight=false,transitions=0,lastRule=null],firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=1,YEAR=2019,MONTH=5,WEEK_OF_YEAR=23,WEEK_OF_MONTH=2,DAY_OF_MONTH=6,DAY_OF_YEAR=157,DAY_OF_WEEK=5,DAY_OF_WEEK_IN_MONTH=1,AM_PM=0,HOUR=7,HOUR_OF_DAY=7,MINUTE=36,SECOND=6,MILLISECOND=705,ZONE_OFFSET=0,DST_OFFSET=0] 2019-06-06 07:36:06.713+ [id=77]FINEo.j.p.p.Cron#checkTriggers: cron checking somejob2 2019-06-06 07:36:06.713+ [id=77]FINEo.j.p.p.ParameterizedTimerTrigger#checkCronTabsAndRun: checking and maybe running at
[JIRA] (JENKINS-57148) hudson.model.Queue#maintain doesn't handle exceptions properly and cause queue stuck
Title: Message Title Alexey Grigorov closed an issue as Not A Defect Jenkins / JENKINS-57148 hudson.model.Queue#maintain doesn't handle exceptions properly and cause queue stuck Change By: Alexey Grigorov Status: Open Closed Resolution: Not A Defect 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-57148) hudson.model.Queue#maintain doesn't handle exceptions properly and cause queue stuck
Title: Message Title Alexey Grigorov commented on JENKINS-57148 Re: hudson.model.Queue#maintain doesn't handle exceptions properly and cause queue stuck after digging into a source code of a authorize-project plugin I actually found that exception handled there org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy.java:196 so this ticket is not valid I am closing it 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-57148) hudson.model.Queue#maintain doesn't handle exceptions properly and cause queue stuck
Title: Message Title Alexey Grigorov created an issue Jenkins / JENKINS-57148 hudson.model.Queue#maintain doesn't handle exceptions properly and cause queue stuck Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-04-22 23:05 Environment: jenkins 2.164.1 Priority: Critical Reporter: Alexey Grigorov Hi Jenkins team We have a situation where we have few hundreds builds in the queue and one of them throws exception in queue.maintain (in our case job authentication is set to user which left and not exist in AD anymore). This exception is not handled inside the loop which iterates over buildable items and because of that all execution of queue.maintain fails, and next time if fails again and again. Other items in the queue which are healthy cannot run or have to wait for hours, because exception is thrown before their turn in queue.maintain and not handled. To my mind there should be exception handling inside a loop of hudson/model/Queue.java:1587 to avoid impact on other queue items processing if just one item is faulty. below is a message we see in the log with frequency of few dozens per second. WARNING: Invalid User someleftuser. Falls back to anonymous. org.acegisecurity.userdetails.UsernameNotFoundException: Authentication was successful but cannot locate the user information for someleftuser at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:392) at
[JIRA] (JENKINS-57004) Error with jira plugin: Request cannot be executed; I/O reactor status: STOPPED
Title: Message Title Alexey Grigorov created an issue Jenkins / JENKINS-57004 Error with jira plugin: Request cannot be executed; I/O reactor status: STOPPED Issue Type: Bug Assignee: Unassigned Attachments: image-2019-04-15-02-55-26-279.png Components: jira-plugin Created: 2019-04-15 00:00 Environment: jenkins 2.164.1 jira plugin 3.0.6 Priority: Critical Reporter: Alexey Grigorov Go to Jira sites in jenkinsURL/configure and when clicking on Validate Settings the following error is returned: java.lang.IllegalStateException: Request cannot be executed; I/O reactor status: STOPPED at org.apache.http.util.Asserts.check(Asserts.java:46) at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase.ensureRunning(CloseableHttpAsyncClientBase.java:90) at org.apache.http.impl.nio.client.InternalHttpAsyncClient.execute(InternalHttpAsyncClient.java:123) at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:75) at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:108) at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient.execute(SettableFuturePromiseHttpPromiseAsyncClient.java:36) at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.doExecute(ApacheAsyncHttpClient.java:417) at
[JIRA] (JENKINS-54988) jenkins queue is locked (not able to start any build) because KubernetesSlave._terminate stuck
Title: Message Title
Alexey Grigorov updated an issue
Jenkins / JENKINS-54988
jenkins queue is locked (not able to start any build) because KubernetesSlave._terminate stuck
Change By:
Alexey Grigorov
Hi guys apparently this call can hang forever and it will hold jenkins queue in locked state so no build will be able to start. [https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesSlave.java#L262]Here is a stacktrace from a threadddump threaddump and a screenshot{noformat}"jenkins.util.Timer [#6] / waiting for JNLP4-connect connection from 10.77.102.75/10.77.102.75:57072 id=77127042" daemon prio=5 TIMED_WAITING java.lang.Object.wait(Native Method) hudson.remoting.Request.call(Request.java:177) hudson.remoting.Channel.call(Channel.java:954) org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave._terminate(KubernetesSlave.java:236) hudson.slaves.AbstractCloudSlave.terminate(AbstractCloudSlave.java:67) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:59) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:43) hudson.slaves.SlaveComputer$4.run(SlaveComputer.java:843) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.slaves.SlaveComputer.setNode(SlaveComputer.java:840) hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:121) hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:46) hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:207) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:190) jenkins.model.Jenkins.updateComputerList(Jenkins.java:1552) jenkins.model.Nodes$6.run(Nodes.java:261) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) jenkins.model.Nodes.removeNode(Nodes.java:252) jenkins.model.Jenkins.removeNode(Jenkins.java:2066) hudson.slaves.AbstractCloudSlave.terminate(AbstractCloudSlave.java:70) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:59) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:43) hudson.slaves.SlaveComputer$4.run(SlaveComputer.java:843) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.slaves.SlaveComputer.setNode(SlaveComputer.java:840) hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:121) hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:46) hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:207) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:190) jenkins.model.Jenkins.updateComputerList(Jenkins.java:1552) jenkins.model.Nodes$6.run(Nodes.java:261) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) jenkins.model.Nodes.removeNode(Nodes.java:252)
[JIRA] (JENKINS-54988) jenkins queue is locked (not able to start any build) because KubernetesSlave._terminate stuck
Title: Message Title
Alexey Grigorov updated an issue
Jenkins / JENKINS-54988
jenkins queue is locked (not able to start any build) because KubernetesSlave._terminate stuck
Change By:
Alexey Grigorov
Hi guys apparently this call can hang forever and it will hold jenkins queue in locked state so no build will be able to start. [https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesSlave.java#L262]Here is a stacktrace from a threadddump and a screenshot {noformat}"jenkins.util.Timer [#6] / waiting for JNLP4-connect connection from 10.77.102.75/10.77.102.75:57072 id=77127042" daemon prio=5 TIMED_WAITING java.lang.Object.wait(Native Method) hudson.remoting.Request.call(Request.java:177) hudson.remoting.Channel.call(Channel.java:954) org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave._terminate(KubernetesSlave.java:236) hudson.slaves.AbstractCloudSlave.terminate(AbstractCloudSlave.java:67) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:59) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:43) hudson.slaves.SlaveComputer$4.run(SlaveComputer.java:843) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.slaves.SlaveComputer.setNode(SlaveComputer.java:840) hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:121) hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:46) hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:207) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:190) jenkins.model.Jenkins.updateComputerList(Jenkins.java:1552) jenkins.model.Nodes$6.run(Nodes.java:261) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) jenkins.model.Nodes.removeNode(Nodes.java:252) jenkins.model.Jenkins.removeNode(Jenkins.java:2066) hudson.slaves.AbstractCloudSlave.terminate(AbstractCloudSlave.java:70) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:59) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:43) hudson.slaves.SlaveComputer$4.run(SlaveComputer.java:843) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.slaves.SlaveComputer.setNode(SlaveComputer.java:840) hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:121) hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:46) hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:207) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:190) jenkins.model.Jenkins.updateComputerList(Jenkins.java:1552) jenkins.model.Nodes$6.run(Nodes.java:261) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) jenkins.model.Nodes.removeNode(Nodes.java:252)
[JIRA] (JENKINS-54988) jenkins queue is locked (not able to start any build) because KubernetesSlave._terminate stuck
Title: Message Title
Alexey Grigorov updated an issue
Jenkins / JENKINS-54988
jenkins queue is locked (not able to start any build) because KubernetesSlave._terminate stuck
Change By:
Alexey Grigorov
Hi guys apparently this call can hang forever and it will hold jenkins queue in locked state so no build will be able to start. [https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesSlave.java#L262]Here is a stacktrace from a threadddump{noformat}"jenkins.util.Timer [#6] / waiting for JNLP4-connect connection from 10.77.102.75/10.77.102.75:57072 id=77127042" daemon prio=5 TIMED_WAITING java.lang.Object.wait(Native Method) hudson.remoting.Request.call(Request.java:177) hudson.remoting.Channel.call(Channel.java:954) org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave._terminate(KubernetesSlave.java:236) hudson.slaves.AbstractCloudSlave.terminate(AbstractCloudSlave.java:67) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:59) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:43) hudson.slaves.SlaveComputer$4.run(SlaveComputer.java:843) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.slaves.SlaveComputer.setNode(SlaveComputer.java:840) hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:121) hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:46) hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:207) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:190) jenkins.model.Jenkins.updateComputerList(Jenkins.java:1552) jenkins.model.Nodes$6.run(Nodes.java:261) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) jenkins.model.Nodes.removeNode(Nodes.java:252) jenkins.model.Jenkins.removeNode(Jenkins.java:2066) hudson.slaves.AbstractCloudSlave.terminate(AbstractCloudSlave.java:70) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:59) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:43) hudson.slaves.SlaveComputer$4.run(SlaveComputer.java:843) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.slaves.SlaveComputer.setNode(SlaveComputer.java:840) hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:121) hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:46) hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:207) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:190) jenkins.model.Jenkins.updateComputerList(Jenkins.java:1552) jenkins.model.Nodes$6.run(Nodes.java:261) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) jenkins.model.Nodes.removeNode(Nodes.java:252) jenkins.model.Jenkins.removeNode(Jenkins.java:2066)
[JIRA] (JENKINS-54988) jenkins queue is locked (not able to start any build) because KubernetesSlave._terminate stuck
Title: Message Title
Alexey Grigorov updated an issue
Jenkins / JENKINS-54988
jenkins queue is locked (not able to start any build) because KubernetesSlave._terminate stuck
Change By:
Alexey Grigorov
Hi guys apparently this call can hang forever and it will hold jenkins queue in locked state so no build will be able to start. [https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesSlave.java#L262]Here is a stacktrace from a threadddump{noformat}"jenkins.util.Timer [#6] / waiting for JNLP4-connect connection from 10.77.102.75/10.77.102.75:57072 id=77127042" daemon prio=5 TIMED_WAITING java.lang.Object.wait(Native Method) hudson.remoting.Request.call(Request.java:177) hudson.remoting.Channel.call(Channel.java:954) org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave._terminate(KubernetesSlave.java:236) hudson.slaves.AbstractCloudSlave.terminate(AbstractCloudSlave.java:67) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:59) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:43) hudson.slaves.SlaveComputer$4.run(SlaveComputer.java:843) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.slaves.SlaveComputer.setNode(SlaveComputer.java:840) hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:121) hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:46) hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:207) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:190) jenkins.model.Jenkins.updateComputerList(Jenkins.java:1552) jenkins.model.Nodes$6.run(Nodes.java:261) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) jenkins.model.Nodes.removeNode(Nodes.java:252) jenkins.model.Jenkins.removeNode(Jenkins.java:2066) hudson.slaves.AbstractCloudSlave.terminate(AbstractCloudSlave.java:70) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:59) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:43) hudson.slaves.SlaveComputer$4.run(SlaveComputer.java:843) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.slaves.SlaveComputer.setNode(SlaveComputer.java:840) hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:121) hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:46) hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:207) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:190) jenkins.model.Jenkins.updateComputerList(Jenkins.java:1552) jenkins.model.Nodes$6.run(Nodes.java:261) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) jenkins.model.Nodes.removeNode(Nodes.java:252) jenkins.model.Jenkins.removeNode(Jenkins.java:2066)
[JIRA] (JENKINS-54988) jenkins queue is locked (not able to start any build) because KubernetesSlave._terminate stuck
Title: Message Title Alexey Grigorov updated an issue Jenkins / JENKINS-54988 jenkins queue is locked (not able to start any build) because KubernetesSlave._terminate stuck Change By: Alexey Grigorov Attachment: 2018-12-01 23_13_46-Jenkins.png 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-54988) jenkins queue is locked (not able to start any build) because KubernetesSlave._terminate stuck
Title: Message Title Alexey Grigorov created an issue Jenkins / JENKINS-54988 jenkins queue is locked (not able to start any build) because KubernetesSlave._terminate stuck Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-12-03 17:38 Priority: Critical Reporter: Alexey Grigorov Hi guys apparently this call can hang forever and it will hold jenkins queue in locked state so no build will be able to start. https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesSlave.java#L262 Here is a stacktrace from a threadddump "jenkins.util.Timer [#6] / waiting for JNLP4-connect connection from 10.77.102.75/10.77.102.75:57072 id=77127042" daemon prio=5 TIMED_WAITING java.lang.Object.wait(Native Method) hudson.remoting.Request.call(Request.java:177) hudson.remoting.Channel.call(Channel.java:954) org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave._terminate(KubernetesSlave.java:236) hudson.slaves.AbstractCloudSlave.terminate(AbstractCloudSlave.java:67) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:59) hudson.slaves.CloudRetentionStrategy.check(CloudRetentionStrategy.java:43) hudson.slaves.SlaveComputer$4.run(SlaveComputer.java:843) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.slaves.SlaveComputer.setNode(SlaveComputer.java:840) hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:121) hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:46) hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:207) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:190)
[JIRA] (JENKINS-54249) GitHub Commit Status Setter - Cannot retrieve Git metadata
Title: Message Title Alexey Grigorov commented on JENKINS-54249 Re: GitHub Commit Status Setter - Cannot retrieve Git metadata +1 org/jenkinsci/plugins/github/util/BuildDataHelper.java:59 it compare github repo name with jekins job name which is epic fail 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-53239) Use default Jetty QueuedThreadPool
Title: Message Title Alexey Grigorov commented on JENKINS-53239 Re: Use default Jetty QueuedThreadPool It would be great to have it back-ported to LTS 2.121.* from where it is started to occur, to have valid upgrade path for LTS releases 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-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title
Alexey Grigorov edited a comment on JENKINS-46507
Re: Parallel Pipeline random java.lang.InterruptedException
Same here. I'm running a @NonCPS labeled method in library and if fails with this error randomly in the middle{code:java}import jenkins.*import jenkins.model.*import hudson.*import hudson.model.*/* This method will find all jobs and verify their disk usage.Then it will remove job runs to fit quotaThat will help to save disk space*/@NonCPSdef call() {def maxRunSize = 21474836480 //20Gbdef maxJobSize = 42949672960 //40GbJenkins.instance.getAllItems(hudson.model.Job).each{println itdef runs = it.getBuilds()def job = itdef totalSize = 0def jobSizeReached = falseruns.each{def currentRun = itdef currentRunSize = it.getRootDir().directorySize()println itprintln currentRunSizeswitch (currentRunSize) { case {it > maxRunSize} : currentRun.delete() println "deleted " + currentRun + " for having size " + it + " over allowed " + maxRunSize break case {it + totalSize > maxJobSize || jobSizeReached } : jobSizeReached = true currentRun.delete() println "deleted " + currentRun + " for not fitting total " + job + " jobs size " + (totalSize+currentRunSize) +" to max allowed " + maxJobSize break default : totalSize += currentRunSize println 'leaving ' + currentRun + ". current total = " + totalSize break}println '--'}println '=='}}{code}{noformat} <> --[Pipeline] echo[Pipeline] End of Pipelinejava.lang.InterruptedException at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1302) at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:275) at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:111) at org.jenkinsci.plugins.workflow.cps.CpsStepContext.getThreadGroupSynchronously(CpsStepContext.java:248) at org.jenkinsci.plugins.workflow.cps.CpsStepContext.getThreadSynchronously(CpsStepContext.java:237) at org.jenkinsci.plugins.workflow.cps.CpsStepContext.doGet(CpsStepContext.java:298) at org.jenkinsci.plugins.workflow.support.DefaultStepContext.get(DefaultStepContext.java:61) at org.jenkinsci.plugins.workflow.steps.StepDescriptor.checkContextAvailability(StepDescriptor.java:258) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:206) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at org.jenkinsci.plugins.workflow.cps.CpsScript.println(CpsScript.java:221) at sun.reflect.GeneratedMethodAccessor1023.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at
[JIRA] (JENKINS-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title
Alexey Grigorov commented on JENKINS-46507
Re: Parallel Pipeline random java.lang.InterruptedException
Same here. I'm running a @NonCPS labeled method in library and if fails with this error randomly in the middle
import jenkins.*
import jenkins.model.*
import hudson.*
import hudson.model.*
/* This method will find all jobs and verify their disk usage.
Then it will remove job runs to fit quota
That will help to save disk space
*/
@NonCPS
def call() {
def maxRunSize = 21474836480 //20Gb
def maxJobSize = 42949672960 //40Gb
Jenkins.instance.getAllItems(hudson.model.Job).each
{
println it
def runs = it.getBuilds()
def job = it
def totalSize = 0
def jobSizeReached = false
runs.each{
def currentRun = it
def currentRunSize = it.getRootDir().directorySize()
println it
println currentRunSize
switch (currentRunSize) {
case {it > maxRunSize} :
currentRun.delete()
println "deleted " + currentRun + " for having size " + it + " over allowed " + maxRunSize
break
case {it + totalSize > maxJobSize || jobSizeReached } :
jobSizeReached = true
currentRun.delete()
println "deleted " + currentRun + " for not fitting total " + job + " jobs size " + (totalSize+currentRunSize) +" to max allowed " + maxJobSize
break
default :
totalSize += currentRunSize
println 'leaving ' + currentRun + ". current total = " + totalSize
break
}
println '--'
}
println '=='
}
}
--
[Pipeline] echo
[Pipeline] End of Pipeline
java.lang.InterruptedException
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1302)
at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:275)
at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:111)
at org.jenkinsci.plugins.workflow.cps.CpsStepContext.getThreadGroupSynchronously(CpsStepContext.java:248)
at org.jenkinsci.plugins.workflow.cps.CpsStepContext.getThreadSynchronously(CpsStepContext.java:237)
at org.jenkinsci.plugins.workflow.cps.CpsStepContext.doGet(CpsStepContext.java:298)
at org.jenkinsci.plugins.workflow.support.DefaultStepContext.get(DefaultStepContext.java:61)
at org.jenkinsci.plugins.workflow.steps.StepDescriptor.checkContextAvailability(StepDescriptor.java:258)
at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:206)
at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153)
at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122)
at
[JIRA] (JENKINS-46248) Deadlock in queue maintenance + node removal
Title: Message Title Alexey Grigorov commented on JENKINS-46248 Re: Deadlock in queue maintenance + node removal I have same problem, deadlocks started to appear daily Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-50712) branchSources in MultibranchWorkflowJob and PipelineJob asking for vulnerable signature approvals when running in sandbox
Title: Message Title Alexey Grigorov updated an issue Jenkins / JENKINS-50712 branchSources in MultibranchWorkflowJob and PipelineJob asking for vulnerable signature approvals when running in sandbox Change By: Alexey Grigorov Summary: branchSources in MultibranchWorkflowJob and PipelineJob asking for vulnerable signature approvals when running in sandbox Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-50712) branchSources in MultibranchWorkflowJob asking for vulnerable signature approvals when running in sandbox
Title: Message Title
Alexey Grigorov created an issue
Jenkins / JENKINS-50712
branchSources in MultibranchWorkflowJob asking for vulnerable signature approvals when running in sandbox
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2018-04-10 10:02
Priority:
Major
Reporter:
Alexey Grigorov
Hi team I have 2 examples where I have parametrized build which supposed to create a pipelines. But when running in sandbox it failing and asking for approvals of : method groovy.lang.GroovyObject getProperty java.lang.String method groovy.lang.GroovyObject invokeMethod java.lang.String java.lang.Object which are highlighted red as dangerous by jenkins here are examples
multibranchPipelineJob("${JENKINS_PROJECT_NAME}/CI Build") {
branchSources {
github {
scanCredentialsId("${GIT_CREDENTIALS_ID}")
repoOwner("${GITHUB_REPO_OWNER}")
repository("${GITHUB_REPO_NAME}")
}
}
}
ERROR: Scripts not permitted to use method groovy.lang.GroovyObject getProperty java.lang.String (javaposse.jobdsl.dsl.helpers.workflow.GitHubBranchSourceContext.GIT_CREDENTIALS_ID)
I think problem here is usage of DELEGATE_FIRST mode without whitelisting (if it even possible to whitelist) second example
