• Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Minor Minor
    • swarm-plugin
    • None
    • 3.30

      Whenever there is a problem with a swarm slave that causes its disconnection the slave just disappears. This prevents on first acknowledging there is a problem with that particular slave and secondly finding out more from logs.

      One possible solution is to have a "sticky" option in slave configuration so to make it persistent in case it goes offline.

      Another possible solution would be to add in general configuration some time based options for "swarm" specific slaves:

      • connection timeout (ex 15 min)
      • removal timeout (ex: 1 day)

      The basic idea is the same, to provide more transparency of the status of slaves instead of hiding them when something goes wrong.

          [JENKINS-20668] Persist Swarm agents when they go offline

          Another use case for persisting swarm slave info is when you configure the slave (eg add tool locations). When a network hiccup occurs the slave automatically reconnects, but lost all its configuration.

          Nico Mommaerts added a comment - Another use case for persisting swarm slave info is when you configure the slave (eg add tool locations). When a network hiccup occurs the slave automatically reconnects, but lost all its configuration.

          Jacob Keller added a comment -

          Another issue I have is similar.

          Say a slave is for some label "node" and goes offline. If no other slave has the label "node" then that label isn't remembered by the Jenkins system. Thus, when a job is edited and saved, it removes the label from the configuration permanently (as it doesn't exist according to the master). This happens for example with a matrix job.

          This is a problem if someone happens to edit a job during a window when a slave is offline, and results in a hidden loss of running on that slave in the matrix job builds.

          Jacob Keller added a comment - Another issue I have is similar. Say a slave is for some label "node" and goes offline. If no other slave has the label "node" then that label isn't remembered by the Jenkins system. Thus, when a job is edited and saved, it removes the label from the configuration permanently (as it doesn't exist according to the master). This happens for example with a matrix job. This is a problem if someone happens to edit a job during a window when a slave is offline, and results in a hidden loss of running on that slave in the matrix job builds.

          Bevan Kling added a comment -

          Would it be possible to add the ability to set the node properties for the following options in the swarm config

          • Node Offline Email Notification
          • Node owners
          • Send email when connected
          • Send email when disconnected
          • Send email on every launch failure
          • Send email on first launch failure
          • Send email when temporary off-line mark applied
          • Send email when temporary off-line mark applied
          • Send email when temporary off-line mark removed

          Bevan Kling added a comment - Would it be possible to add the ability to set the node properties for the following options in the swarm config Node Offline Email Notification Node owners Send email when connected Send email when disconnected Send email on every launch failure Send email on first launch failure Send email when temporary off-line mark applied Send email when temporary off-line mark applied Send email when temporary off-line mark removed

          Oleg Nenashev added a comment -

          KK does not maintain this plugin anymore. Moving to unassigned to set the expectation

          Oleg Nenashev added a comment - KK does not maintain this plugin anymore. Moving to unassigned to set the expectation

          Basil Crow added a comment -

          Fixed in jenkinsci/swarm-plugin#368. Released in 3.30.

          Basil Crow added a comment - Fixed in jenkinsci/swarm-plugin#368 . Released in 3.30 .

            rimitchell Richard
            josesa Jose Sa
            Votes:
            8 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: