Last modified: 2014-10-30 19:49:29 UTC
Bug 47527 requests to report the build status directly in Gerrit. A javascript can be written to fetch the informations from the Zuul status page at https://integration.wikimedia.org/zuul/status.json I am afraid this one is a bit too large though: When there is nothing to report the request takes roughly 800ms and 18178 bytes. By letting Zuul status.json accept a change filter, we could reduce the payload and most probably the download time.
Isn't that API upstream? Or is that .json end point custom configuration that we copied from openstack (like the html status page)
Yup it is upstream but it can be adapted to fit our needs. I will work on a patch that let us query a specific change.
Unassigning self, I got too many bugs right now. Will revisit later on.
Upstream has landed a change that would let one query a specific change https://review.openstack.org/#/c/124390/ > The supported urls are: > - /status: return a complex data structure that represents the entire > queue / pipeline structure of the system > - /status.json (backwards compatibility): same as /status > - /status/change/X,Y: return status just for gerrit change X,Y Gotta upgrade our Zuul version.
I am now upgrading Zuul which bring the upstream change. We will most probably need to adjust the zuul_proxy Apache configuration file on gallium (via puppet).
Change 170070 had a related patch set uploaded by Hashar: contint: Zuul status learned to query a single change https://gerrit.wikimedia.org/r/170070
Created attachment 16957 [details] json result for /stats/change/170067,1 We can now fetch the status of an individual change using: https://integration.wikimedia.org/zuul/status/change/170067,1 See attached output for an example.
This has been deployed in production. Will let us implement: Bug 47527 - Status update in Gerrit of current queued commit/testing request
Change 170070 merged by Dzahn: contint: Zuul status learned to query a single change https://gerrit.wikimedia.org/r/170070
