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

Long-running job times out, but we have no timeout configured

    Details

    • Similar Issues:

      Description

      We use a Jenkins parameterized pipeline job to build new VMs via Terraform and then configure them with an Ansible playbook via Ansible Tower.  The playbook takes a long time to complete (40-45 minutes), and Jenkins appears to be timing out before it finishes:

      Error: Monitoring aborted due to timeout.

      The issue doesn't appear to be with the Ansible Tower job; it continues running for a few more minutes until it completes successfully.

      We do not have the build-timeout plugin configured, and I haven't been able to find any other global timeout setting in the Jenkins configuration.  It's worth noting that the step of the playbook that it's timing out on is a "yum update" that reports no output for a long time, so perhaps Jenkins assumes the task has failed when it doesn't get any output for several minutes?  Is there a way to disable this behavior?  Thanks!!!

        Attachments

          Activity

          Hide
          matthearncsc Matt Hearn added a comment -

          Turns out the issue is actually with the "tower-cli" that we use to kick off the jobs in Tower; while Tower doesn't have a timeout set, tower-cli does.  The problem isn't with Jenkins, so I'm closing.  Thanks!!!

          Show
          matthearncsc Matt Hearn added a comment - Turns out the issue is actually with the "tower-cli" that we use to kick off the jobs in Tower; while Tower doesn't have a timeout set, tower-cli does .  The problem isn't with Jenkins, so I'm closing.  Thanks!!!

            People

            • Assignee:
              gront Daniel Gront
              Reporter:
              matthearncsc Matt Hearn
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: