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

Error in the init-script is causing infinite re-spawning of droplets

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • digitalocean-plugin
    • None

      Using the DigitalOcean plugin I'm adding a droplet type under Manage Jenkins -> Configure System, and then I'm starting a new job that uses it.

      If the init script of the droplet has a bug and Jenkins is unable to log into this droplet (for example because the connecting port is not up yet), then the digitalocean-plugin keeps doing the following in an infinite loop:
      1. killing the droplet
      2. spawning a new droplet

      These short-lived droplets are each billed for the minimum time, which is 1h. What this means is that because of this respawning loop, within one hour it's possible to be billed even 60h!

      Any idea how to mitigate this behaviour?

          [JENKINS-38379] Error in the init-script is causing infinite re-spawning of droplets

          Bert Goethals added a comment -

          I would say that this is expected behaviour. It would be difficult for Jenkins to figure out WHY it fails to connect to the remote Computer. So when it fails to connect within the (configurable) connection time, it retries to boot a machine.

          What type of behaviour would you prefer to see to limit this?

          Bert Goethals added a comment - I would say that this is expected behaviour. It would be difficult for Jenkins to figure out WHY it fails to connect to the remote Computer. So when it fails to connect within the (configurable) connection time, it retries to boot a machine. What type of behaviour would you prefer to see to limit this?

            Unassigned Unassigned
            jimis jimis jimis
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: