Age | Commit message (Collapse) | Author | Files | Lines |
|
more often, run pbuilder setup jobs less often
|
|
giving up, also fail gracefully
|
|
|
|
everywhere and always use diffoscope
|
|
|
|
|
|
same for pbuilder bases?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(but dont use that feature yet)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
https://summit.debconf.org/debconf15/meeting/186/jenkinsdebianorg-session/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
speed up our repo, maybe.
|
|
|
|
|
|
|
|
|
|
material (=lunars latest talk)
|
|
This moves all the limits handling to a dedicated class and the data to a
dedicated object, instead of embedding them into the scheduling code, where
they are hard to find and to edit.
|
|
|
|
|