> The easy way to get a result bundle hash of a job is by constructing URL
> like https://validation.linaro.org/lava-server/scheduler/job/46594/json
> . That's suitable for both web client site programming, and backend
> programming. Unfortunately, the latter case breaks when jobs is
> submitted to private stream - the URL gives 403 then and required OpenID
> auth to succeed. It would be quite a chore to emulate OpenID auth
> programmatically in backend app. Instead, there should be XMLRPC call to
> get a result bundle id of a particular job. It probably also makes sense
> to add getters for other job properties like status, etc. (or one getter
> for several props).
Seems reasonable -- and should easy enough. Want to try it yourself?
Otherwise we should get to it soonish I hope.
Paul Sokolovsky <email address hidden> writes:
> The easy way to get a result bundle hash of a job is by constructing URL /validation. linaro. org/lava- server/ scheduler/ job/46594/ json
> like https:/
> . That's suitable for both web client site programming, and backend
> programming. Unfortunately, the latter case breaks when jobs is
> submitted to private stream - the URL gives 403 then and required OpenID
> auth to succeed. It would be quite a chore to emulate OpenID auth
> programmatically in backend app. Instead, there should be XMLRPC call to
> get a result bundle id of a particular job. It probably also makes sense
> to add getters for other job properties like status, etc. (or one getter
> for several props).
Seems reasonable -- and should easy enough. Want to try it yourself?
Otherwise we should get to it soonish I hope.