Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Hudson » Job aborted when updating the config.xml from API
Job aborted when updating the config.xml from API [message #1705059] Tue, 11 August 2015 16:43 Go to next message
Michael Yang is currently offline Michael YangFriend
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
Re: Job aborted when updating the config.xml from API [message #1705082 is a reply to message #1705059] Tue, 11 August 2015 22:55 Go to previous messageGo to next message
Winston Prakash is currently offline Winston PrakashFriend
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
Re: Job aborted when updating the config.xml from API [message #1705163 is a reply to message #1705082] Wed, 12 August 2015 14:11 Go to previous messageGo to next message
Michael Yang is currently offline Michael YangFriend
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.
Re: Job aborted when updating the config.xml from API [message #1705177 is a reply to message #1705163] Wed, 12 August 2015 15:50 Go to previous messageGo to next message
Winston Prakash is currently offline Winston PrakashFriend
Messages: 534
Registered: August 2011
Location: Fremont, CA USA
Senior Member
It behaves the same way. Underneath the same API is used.

Winston Prakash
Eclipse Hudson team
Re: Job aborted when updating the config.xml from API [message #1705406 is a reply to message #1705177] Fri, 14 August 2015 18:14 Go to previous message
Michael Yang is currently offline Michael YangFriend
Messages: 5
Registered: August 2015
Junior Member
That's weird then, because the config can be updated from the web page when the job is building.
Previous Topic:Online Hudson Java API documents?
Next Topic:Mobile usability improvement (not-yet official project)
Goto Forum:
  


Current Time: Fri Oct 11 03:35:39 GMT 2024

Powered by FUDForum. Page generated in 0.03692 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top