Take advantage of more efficient /experimental/jobs/id/status route

[kalikiana]

Requests could be made more efficient by using the not well-known /experimental/jobs/id/status route.

[grisu48]

Thanks for reporting!

Note for myself: Here's an example reply:

{"blocked_by_id":null,"id":10825965,"result":"none","state":"running"}

(also it's blazing fast!)

[grisu48]

The gopenqa library introduced GetJobState in release 0.7.0

[grisu48]

@kalikiana what is the status of this feature in openQA? Is it still experimental? Is it possible to pass multiple jobs or do we need to do one request per job?

[kalikiana]

@kalikiana what is the status of this feature in openQA? Is it still experimental? Is it possible to pass multiple jobs or do we need to do one request per job?

It is still experimental. Since the job is part of the path the API probably needs to be changed to support multiple jobs? I'd say open a ticket

[grisu48]

@kalikiana what is the status of this feature in openQA? Is it still experimental? Is it possible to pass multiple jobs or do we need to do one request per job?

It is still experimental. Since the job is part of the path the API probably needs to be changed to support multiple jobs? I'd say open a ticket

Ok thanks for the update!