[JIRA] (JENKINS-38379) Error in the init-script is causing infinite re-spawning of droplets
Title: Message Title Bert Goethals commented on JENKINS-38379 Re: Error in the init-script is causing infinite re-spawning of droplets 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? 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-38379) Error in the init-script is causing infinite re-spawning of droplets
Title: Message Title jimis jimis created an issue Jenkins / JENKINS-38379 Error in the init-script is causing infinite re-spawning of droplets Issue Type: Bug Assignee: Unassigned Components: digitalocean-plugin Created: 2016/Sep/20 1:55 PM Priority: Major Reporter: jimis jimis 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? Add Comment
