|
|
| Re: Hudson job build ID [message #1058365 is a reply to message #1058356] |
Mon, 13 May 2013 17:51  |
 mauricio martins
Messages: 2
Registered: May 2013 |
Junior Member |
|
|
No.. it doesn't work. I can't set this value when submitting the job, creating a traceability of the request.
Just to explay better, here's an excerpt of the request IN QUEUE in JSON format (sensitive fields trimmed):
{"items":[{"actions":[{"parameters":[---TRIMMED---]},{"causes":[{"shortDescription":"Started by user XXXX","userName":"XXX"}]}],"blocked":false,"buildable":false,"params":"---TRIMMED---","stuck":false,"task":{"name":"JOBNAME","url":"http_:_//<server>/hudson/job/JOBNAME/","color":"blue"},"why":"In the quiet period. Expires in 1.3 sec","timestamp":1368466145782}]}
Now the request when executed
{"actions":[{"parameters":[]},{"causes":[]},{}],"artifacts":[],"building":false,"description":null,"duration":47023,"fullDisplayName":"JOBNAME #419","id":"2013-05-13_12-29-05","keepLog":false,"number":419,"result":"SUCCESS","timestamp":1368466145805,"url":"http_:_//SERVER/hudson/job/JOBNAME/419/","builtOn":"","changeSet":{"items":[],"kind":null},"culprits":[]}
See the field id, it's the BUILD_ID... I supposed "timestamp" never changed... but it changes. There's no means to properly identify both records in the hudson job execution lifecycle unless doing the parameter comparison, assuming no one submitted same job twice in a short period of time...
|
|
|
Powered by
FUDForum. Page generated in 0.03309 seconds
] 
Search
Help
Register
Login
Home
