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

Jenkins Job is aborted when job configuration changes


      If I have a running job, and I make a configuration change to the job... when I hit save, it is aborting the current job. It should simply make the changes for the NEXT run of the job. This did not always behave this way:

      I am running in a master / slave set up, but I don't know if that's applicable. Master log:
      Triggering win64.sql
      win64.sql appears to be cancelled
      win64.sql completed with result ABORTED
      Finished: ABORTED

      The slave log is deleted and can't be seen.

            r2b2_nz Richard Bywater
            w25r William Lichtenberger
            1 Vote for this issue
            3 Start watching this issue