-
Bug
-
Resolution: Incomplete
-
Critical
-
Windows
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.
[JENKINS-14450] Jenkins Job is aborted when job configuration changes
Component/s | New: core [ 15593 ] | |
Component/s | Original: configure-job-column [ 16539 ] | |
Assignee | Original: jieryn [ jieryn ] |
Component/s | New: htmlpublisher [ 15681 ] | |
Component/s | Original: core [ 15593 ] |
Priority | Original: Major [ 3 ] | New: Critical [ 2 ] |
Workflow | Original: JNJira [ 145086 ] | New: JNJira + In-Review [ 176267 ] |
Assignee | New: Richard Bywater [ r2b2_nz ] | |
Resolution | New: Incomplete [ 4 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |