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

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major
    • Component/s: remoting
    • Environment:

      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.

            Assignee:
            Unassigned
            Reporter:
            John Burrows
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: