Re: Maven builds out of control

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Re: Maven builds out of control

Christofer Dutz
Hi all,

Well you could probably self-limit your builds.

I know that when using Jenkinsfiles you can define tags for nodes the build runs on.
So you could probably limit these to a hand full of "H??" nodes and it should not use up all of the resources.


Am 17.08.20, 10:23 schrieb "Arnaud Héritier" <[hidden email]>:

    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 :
    What are the rules to have a dedicated one ?

    On Mon, Aug 17, 2020 at 10:02 AM Michael Osipov <[hidden email]> 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: [hidden email]
    > For additional commands, e-mail: [hidden email]

    Arnaud Héritier
    Twitter/Skype : aheritier

To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]