Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-53320

Job fails because JiraSCMListener times out on too many changes

    XMLWordPrintable

Details

    Description

      If there are too many changes (in our case more than 1000 commits), the JiraSCMListener times out and fails the job.

      java.util.concurrent.TimeoutException: Timeout waiting for task.
      	at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:259)
      	at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:91)
      	at com.google.common.util.concurrent.ForwardingFuture.get(ForwardingFuture.java:69)
      	at com.atlassian.jira.rest.client.internal.async.DelegatingPromise.get(DelegatingPromise.java:107)
      	at hudson.plugins.jira.JiraRestService.getIssuesFromJqlSearch(JiraRestService.java:177)
      	at hudson.plugins.jira.JiraSession.getIssuesFromJqlSearch(JiraSession.java:136)
      	at io.jenkins.blueocean.service.embedded.jira.JiraSCMListener.onChangeLogParsed(JiraSCMListener.java:43)
      	at org.jenkinsci.plugins.workflow.job.WorkflowRun.onCheckout(WorkflowRun.java:1036)
      	at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$1400(WorkflowRun.java:143)
      	at org.jenkinsci.plugins.workflow.job.WorkflowRun$SCMListenerImpl.onCheckout(WorkflowRun.java:1239)
      	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:127)
      	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85)
      	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75)
      	at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
      	at hudson.security.ACL.impersonate(ACL.java:290)
      	at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
      	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
      	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      	at java.lang.Thread.run(Thread.java:745)
      

      Attachments

        Activity

          jglick Jesse Glick added a comment -

          these listeners are async process, running in separate thread

          Acc. to the stack trace the problem occurs synchronously in the step execution thread.

          jglick Jesse Glick added a comment - these listeners are async process, running in separate thread Acc. to the stack trace the problem occurs synchronously in the step execution thread.
          olamy Olivier Lamy added a comment -

          corresponding Jira plugin pr is here https://github.com/jenkinsci/jira-plugin/pull/166 

          olamy Olivier Lamy added a comment - corresponding Jira plugin pr is here https://github.com/jenkinsci/jira-plugin/pull/166  
          vivek Vivek Pandey added a comment -

          olamy AFAIK, these listeners are async process, running in separate thread, a runtime exception can fail that listener, shouldn’t fail the build thought. cc: jglick

          vivek Vivek Pandey added a comment - olamy AFAIK, these listeners are async process, running in separate thread, a runtime exception can fail that listener, shouldn’t fail the build thought. cc: jglick
          olamy Olivier Lamy added a comment -

          vivek this pr will avoid to fail the build  https://github.com/jenkinsci/blueocean-plugin/pull/1816  .

          Can be a first workaround quick fix until better changes in Jira plugin.

          But anyway we need this as timeout can happen all the time while querying Jira so we must not fail the build in this case...

          olamy Olivier Lamy added a comment - vivek this pr will avoid to fail the build   https://github.com/jenkinsci/blueocean-plugin/pull/1816   . Can be a first workaround quick fix until better changes in Jira plugin. But anyway we need this as timeout can happen all the time while querying Jira so we must not fail the build in this case...
          vivek Vivek Pandey added a comment -

          olamy Yeah timeout exception should not fail a build. That needs to be fixed.

          vivek Vivek Pandey added a comment - olamy Yeah timeout exception should not fail a build. That needs to be fixed.

          People

            olamy Olivier Lamy
            tario Patrick Ruckstuhl
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: