Eclipse Community Forums: Hudson » Job aborted when updating the config.xml from API

Help

Home

Home » Archived » Hudson » Job aborted when updating the config.xml from API

Show: Today's Messages :: Show Polls :: Message Navigator

Job aborted when updating the config.xml from API [message #1705059]

Tue, 11 August 2015 16:43

Michael Yang

Messages: 5
Registered: August 2015

Junior Member

When the job is in progress of building, sending the API to update it's config.xml will get the job interrupted. This marks the job as RED, but no error messages are displayed anywhere.

Is there a requirement that we should only update the config.xml from API when the job is idle ? Sometimes need to update tens of jobs in batches from script, hard to wait until all jobs are in idle.

Thanks for the help.
Hudson version; 3.3.0

Report message to a moderator

Re: Job aborted when updating the config.xml from API [message #1705082 is a reply to message #1705059]

Tue, 11 August 2015 22:55

Winston Prakash

Messages: 534
Registered: August 2011
Location: Fremont, CA USA

Senior Member

When you send the config.xml to Hudson, the Job object is immediately updated with the data in the posted XML. Since the Job object is involved in the build, updating the Job object causing the build to interrupt. Since the build lost reference to the original object, the build stops, but I guess nothing is logging the interruption.

Unfortunately, since Hudson immediately update the job object, the Job should not be updated when it is building, else the build will unexpectedly interrupted.

Winston Prakash
Eclipse Hudson team

Report message to a moderator

Re: Job aborted when updating the config.xml from API [message #1705163 is a reply to message #1705082]

Wed, 12 August 2015 14:11

Michael Yang

Messages: 5
Registered: August 2015

Junior Member

Thank you very much for confirming. That's why I'm thinking about to wrap the API to perform additional check if the last build is in "building" to move on updating.

But how does the config update work from web UI when the job is building? My assumption was they should behave the same way if both goes via API.

Report message to a moderator