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

When a build is aborted, Hudson does not kill all the descendant processes recursively to avoid run-away processes on the Slave Build machines.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • remoting
    • None

      Build job setup to run as "ant.bat -f scm.xml". Ant batch file sets environment variables and kicks off ANT build. While build running, abort is clicked and job aborts normally in Hudson Master as indicated in log/console output:
      Build was aborted
      Finished: ABORTED

      But, on Slave machine, the Ant/Java process doing build still runs to completion, the descendent processes that were running were not killed properly on Slave to truely abort the build.

            Unassigned Unassigned
            jburrows John Burrows
            Votes:
            15 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated: