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

Builds Are Aborted Without Cause or Interaction

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Incomplete
    • Icon: Major Major
    • core
    • None
    • Platform: Other, OS: Linux

      Currently running Hudson 1.315 on Ubuntu 8.04 with two SSH slaves (also Ubuntu
      8.04).

      Hudson is commonly aborting maven builds for no reason usually immediately
      following an SCM checkout. It gives no reason, error or debug information.
      Below is a snipit of code from the end of an auto-aborted build:

      ----------------------------------------------

      At revision 259632
      no change for http://my.private.url/trunk/project since the previous build
      Parsing POMs
      ERROR: Aborted
      Finished: ABORTED

      ----------------------------------------------

      I tried turning on the Audit Trail plugin which was of no help. Also the hudson
      logs do not show anything of importance. They just state the fact that the build
      was aborted.

            Unassigned Unassigned
            clark_malmgren clark_malmgren
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: