Am Montag, den 18.05.2020, 17:50 +0200 schrieb Jonas Hahnfeld: > Am Montag, den 18.05.2020, 12:59 +0200 schrieb Jonas Hahnfeld: > > Am Montag, den 18.05.2020, 11:53 +0100 schrieb Kevin Barry: > > > On Mon, May 18, 2020 at 11:29:35AM +0100, James Lowe wrote: > > > > Countdown.py (which is Jonas' great cli tool) it's what you see when I > > > > do > > > > the countdown (that's literally cut/paste). > > > > > > I haven't seen that script, but the gitlab API exposes pipeline > > > information. It should be enough to correlate a merge request with a > > > pipeline status (running, pending, success, failed, etc). > > > > For reference, it's here: > > https://gitlab.com/lilypond/infrastructure/-/blob/master/countdown.py > > > > > > The API does expose this information, but the script needs to query the > > pipeline status per merge request as it's not included in the list of > > MRs. That sounds expensive, I have to experiment with this. > > See > https://gitlab.com/lilypond/infrastructure/-/merge_requests/5 > > > With a few tweaks I got this into an acceptable range, but it still > takes up to 10 seconds for ~20 merge requests. That's the cost you pay > for O(n) requests to the API and parsing all that response data...
To make this less ambiguous: The time scales with the number of merge requests that have label Patch::new. Right now, this is zero (good job, James!) so for testing I waived this "optimization".
signature.asc
Description: This is a digitally signed message part
