If we are consuming too much resources couldn't we have a dedicated Jenkins controller and/or limit our agents capacities to be the one ones to be impacted by these problems instead of all the users or this Jenkins controller ? Beam, Cassandra, CouchDB and few more have a dedicated controller : https://jenkins-ccos.apache.org/job/masters/ What are the rules to have a dedicated one ?
On Mon, Aug 17, 2020 at 10:02 AM Michael Osipov <micha...@apache.org> wrote: > Am 2020-08-17 um 09:55 schrieb Olivier Lamy: > > Furthermore, we need to clean up unused branches. > > What about removing branches older than 1yo? > > Then older than 6months? > > I consider branches which have been merged obsolete, but there is no > hard rule that an unmerged branch is obsolete. It may prepresent an > unfished state or something which was not agreed on. Dropping work does > not feel right. It needs to be decided on a case-by-case approach. > I have done this recently for Wagon and Resolver. > > Michael > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Arnaud Héritier Twitter/Skype : aheritier
