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

Killing process tree does not work anymore on slave nodes

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • Master: WinXP SP3, Hudson 1.379 (but also affects some earlier versions)
      Slave: Ubuntu 9.04

      Hudson's process tree killerfeature should kill all processes that were initiated during a build to avoid "left-overs" piling up in the process table.

      This feature ceased to work - at least on slave nodes - starting with SVN revision 34736.


      Reproduction

      1. Add new slave node to master.
      2. Create a freestyle project that starts a process that will remain running even after the build has been completed, e.g. with a "shell script" build step "xclock &".
      3. Run that project on the slave node.


      Observed behaviour

      1. xclock is started and will remain open, even after the build has been completed.


      Desired behaviour

      1. xclock is started - and killed again after the build has been completed.

            swiest Simon Wiest
            swiest Simon Wiest
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: