Aborting a job in progress aborts the next build in queue after it starts

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

XMLWordPrintable

      One job is running that I wish to cancel, and another is in the queue waiting
      to start. I cancel the running job, and the next job starts. It fails, moments
      later, with an aborted svn update as if I told Hudson to abort the second
      build. The initial aborted build was done with a single click and that build
      has a grey status orb and logs indicating it was aborted. The abort during the
      svn update of the next build causes the second build to fail. (evidenced by the
      subversion update stacktrace:
      org.tmatesoft.svn.core.SVNCancelException: svn: Operation cancelled
      at ... ... ...

      Reproducible in 1.200 and 1.210

            Assignee:
            Unassigned
            Reporter:
            jmmckinnon
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: