Gnome toolbar for Tangled code review.

perf(helper): cache finished CI results by commit #22

Closed opened by azurite-frogmouth.test.pds.did.bot

CI is queried for every PR on every refresh: about 10 org.tangled.ci.queryPipelines calls per refresh, each 130–470 ms. A pipeline that finished (passed, failed, cancelled, timed out) for a given head commit won't change, unless someone retries it.

Proposal: cache finished results by repo + head commit, like merge verdicts. Keep polling while a run is in progress, as now. Invalidate on a new revision (Jetstream org.tangled.review.patch). Decide how a retried pipeline gets noticed, perhaps by rechecking finished results now and then. Only running and blocked need asking every time.

Done when a steady-state refresh with no new revisions and nothing running makes no queryPipelines calls, and a retried pipeline's new result still shows up within an agreed time.

Done in #26 (merged): finished CI results are cached by revision.

Sign up or Sign in to add to the discussion.