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

Retention time does not respect long running tasks

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • _unsorted
    • Jenkins - 2.121.1
      Azure Commons - 0.2.6
      Azure Credentials - 1.6.0
      Azure Slave Plugin - 0.3.4
      Azure VM Agents - 0.7.1

      We set the retention time for one of our images to 1 hour, but the plan itself takes up to 4 hours.

      The node gets removed after the retention time but the node is not idle nor failing. After the node removal, the plan is left running and not doing anything forever (we have plans running for days).

      Is a huge problem since the nodes we spin up are very expensive so we want to keep them alive as less as possible to perform the build and shutdown if there are no more builds queuing. So our current workaround of setting the retention time higher than the build duration is more than sub-optimal.

      See attached pictures for more info.

            azure_devops Azure DevOps
            edupo Eduardo Lezcano
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: