From: lucas@debian.org 
  
 On 25/08/25 at 23:20 +0200, Lucas Nussbaum wrote: 
 > On 25/08/25 at 13:43 -0700, Otto Kek€l€inen wrote: 
 > > Hi, 
 > > 
 > > > On 24/08/25 at 12:18 -0700, Otto Kek€l€inen wrote: 
 > > ... 
 > > > > I just noticed one developer pushed git commits to 493 different 
 > > > > packages in Salsa, triggering hundreds of Salsa CI pipelines. 
 > > > 
 > > > I think that was me (during adding debian/gbp.conf files to many 
 > > > packages, during DEP-14 migration). 
 > > 
 > > Could you perhaps limit your updates to maybe max 100 commits per day? 
  
 Thinking a bit more about it, for such tasks that involve iterating over 
 many packages, it would be interesting to have an API endpoint one could 
 poll to get an indication of ci-runners' load, or queue length, or 
 whatever. That way it would be easy to just sleep for a while and then 
 try again later. 
  
 According to 
 https://stackoverflow.com/questions/73528678/gitlab-analyze-job- 
 ueue-waiting-time, 
 Salsa exposes such endpoints to admins (probably with too much 
 information for a publicly-accessible endpoint). 
  
 Also it's surprising that GitLab doesnt implement some kind of fairness 
 in its queue management (balance the queue per user, per group, etc.). 
  
 Lucas 
  
 --- SoupGate-Win32 v1.05 
  * Origin: you cannot sedate... all the things you hate (1:229/2)