Please add XMLRPC call for "get job result bundle"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
LAVA Scheduler (deprecated) |
Fix Released
|
High
|
Senthil Kumaran S |
Bug Description
The easy way to get a result bundle hash of a job is by constructing URL like https:/
This came up when finishing deployment of CBuild/LAVA, and adhering to previously missed requirement of tight control of access to toolchain benchmark results produced by restrictive-license benchmarks like EEMBC and SPEC2000. So, this blocks full deployment of CBuild/LAVA, so please treat this with high priority. Thanks.
Related branches
- Linaro Validation Team: Pending requested
-
Diff: 41 lines (+34/-0)1 file modifiedlava_scheduler_app/api.py (+34/-0)
Changed in lava-scheduler: | |
importance: | Undecided → High |
assignee: | nobody → Senthil Kumaran S (stylesen) |
milestone: | none → 2013.05 |
status: | New → In Progress |
Changed in lava-scheduler: | |
status: | In Progress → Fix Committed |
Changed in lava-scheduler: | |
status: | Fix Committed → Fix Released |
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.