-
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
William Lichtenberger
added a comment - We've just discovered that this error is actually due to the HTML Publisher plug in.
In order to reproduce, create a master / slave job that does anything (to proove this I ran a groovy script that sleeped for 30 seconds). Then have it archive an HTML report when the job is done.
After you've done those two steps, now any changes that are made to the jobs configuration will cause the current running jobs to be aborted on the slaves.
------------SLAVE OUTPUT--------------
Sleeping....
Sleeping....
Status Code: 404
Exception:
Stacktrace:
(none)
Generated by Winstone Servlet Engine v0.9.10 at Fri Apr 05 17:45:54 CDT 2013
------------SLAVE OUTPUT--------------
William Lichtenberger
added a comment - We've just discovered that this error is actually due to the HTML Publisher plug in.
In order to reproduce, create a master / slave job that does anything (to proove this I ran a groovy script that sleeped for 30 seconds). Then have it archive an HTML report when the job is done.
After you've done those two steps, now any changes that are made to the jobs configuration will cause the current running jobs to be aborted on the slaves.
------------ SLAVE OUTPUT --------------
Sleeping....
Sleeping....
Status Code: 404
Exception:
Stacktrace:
(none)
Generated by Winstone Servlet Engine v0.9.10 at Fri Apr 05 17:45:54 CDT 2013
------------ SLAVE OUTPUT -------------- William Lichtenberger
added a comment - Better steps to reproduce:
1) Create a master-slave job that uses the HTML Publisher plugin to archive an html file. (I always select Keep past HTML reports)
2) Start the job.
3) While the job is still running on the slave, modify the configuration of the job (in any way).
4) As soon as you save / apply, the job will be aborted.
William Lichtenberger
added a comment - Better steps to reproduce:
1) Create a master-slave job that uses the HTML Publisher plugin to archive an html file. (I always select Keep past HTML reports)
2) Start the job.
3) While the job is still running on the slave, modify the configuration of the job (in any way).
4) As soon as you save / apply, the job will be aborted. 
Richard Bywater
added a comment - Hi - this issue has been around and not touched for a year or more. In an effort to try and focus on issues which are still present, I am resolving these issues for now.
If you feel that the issue is still present, please feel free to re-open / comment. I'll be closing off any issues that haven't had any re-opening or comments by the end of the month.
Thanks for reporting these issues - hopefully you are still using HTML Publisher and its working for you but, if not, let me know so that I can focus on issues that are causing you problems today 
Richard Bywater
added a comment - Hi - this issue has been around and not touched for a year or more. In an effort to try and focus on issues which are still present, I am resolving these issues for now.
If you feel that the issue is still present, please feel free to re-open / comment. I'll be closing off any issues that haven't had any re-opening or comments by the end of the month.
Thanks for reporting these issues - hopefully you are still using HTML Publisher and its working for you but, if not, let me know so that I can focus on issues that are causing you problems today 
This is a core issue, not a configure-job-column-plugin problem.