No I agree, it's a long term solution and orthogonal on cleaning our
branches/builds and limiting our usages
If these are static agents the best we could do at the CI level is to
restrict the usage of our builds to a limited number of agents
traditional slaves
I have a goal to help moving to kubernetes but this will not fix this
problem :)
On Mon, 17 Aug 2020 at 16:46, Arnaud Héritier wrote:
> Thanks for the feedback Gavin, it makes a lot of sense to me.
> The new infrastructure is a traditional one (ie not hosted on Kubernetes) ?
Thanks for the feedback Gavin, it makes a lot of sense to me.
The new infrastructure is a traditional one (ie not hosted on Kubernetes) ?
On Mon, Aug 17, 2020 at 10:44 AM Gavin McDonald
wrote:
> Hi,
>
> On Mon, Aug 17, 2020 at 10:35 AM Olivier Lamy wrote:
>
> > +infra
> >
> > On Mon, 17 Aug
Thanks,
>
> Maarten
>
> > -- Forwarded message -----
> > From: Richard Eckart de Castilho
> > Date: Mon, 17 Aug 2020 at 15:37
> > Subject: Re: Maven builds out of control
> > To:
> >
> >
> > Dear Maven developers,
>
Hi,
On Mon, Aug 17, 2020 at 10:35 AM Olivier Lamy wrote:
> +infra
>
> On Mon, 17 Aug 2020 at 4:23 pm, Arnaud Héritier
> wrote:
>
>> 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
>>
>>
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.
Chris
Am 17.08.20, 10:23 schrieb
to filter those out.
Thanks,
Maarten
-- Forwarded message -
From: Richard Eckart de Castilho
Date: Mon, 17 Aug 2020 at 15:37
Subject: Re: Maven builds out of control
To:
Dear Maven developers,
please fix or disable your CI builds ... other people need to use the
servers
+infra
On Mon, 17 Aug 2020 at 4:23 pm, Arnaud Héritier wrote:
> 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
>
>
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 :
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
-
From: Richard Eckart de Castilho
Date: Mon, 17 Aug 2020 at 15:37
Subject: Re: Maven builds out of control
To:
Dear Maven developers,
please fix or disable your CI builds ... other people need to use the
servers as well and in particular those who need to test jobs as part
Hi!
On Wed, Jul 22, 2020 at 10:29 AM Robert Scholte
wrote:
>
>
> *Robert Scholte:*
> That's very unlikely. I expect that Jenkins itself got an update of that
> plugin and that our MultiBranch setup picked up that change.
>
hm, we don't normally do out of band plugin upgrades unless its'
On 22-7-2020 09:56:16, Gavin McDonald wrote:
Hi Robert,
On Tue, Jul 21, 2020 at 8:26 PM Robert Scholte wrote:
> 2020-07-09_20-33-20
>
>
> 2020-07-21_11-38-13
>
>
Ok so that implies someone on your end made a config change?
Robert Scholte:
That's very unlikely. I expect that Jenkins itself
Hi Robert,
On Tue, Jul 21, 2020 at 8:26 PM Robert Scholte wrote:
> 2020-07-09_20-33-20
>
>
> 2020-07-21_11-38-13
>
>
Ok so that implies someone on your end made a config change?
>
>
> This caused new configuration for *all* our branches and triggered new
> builds.
> The Ubuntu builds were
2020-07-09_20-33-20
2020-07-21_11-38-13
This caused new configuration for *all* our branches and triggered new builds.
The Ubuntu builds were often ready, but a lot were still waiting for Windows
Executors.
Most of these builds are quite short so under normal circumstances there
shouldn't
Looking at it.
It seems like most are waiting for a Windows executor, but these are all taken
too.
Need to investigate a bit more, but it looks like all branches are triggered
for some reason.
That's weird, because we didn't touch are shared Jenkins scripts
Robert
On 21-7-2020 18:22:12, Gavin
Hi Maven folks,
Over 800 builds in the Jenkins queue right now, most of them Maven - and
its been above 500 , mostly Maven for over 12 hours now - Please take a
look and see what is going on ASAP, or I might have to cancel all Maven
jobs to allow other projects to proceed
--
*Gavin McDonald*
17 matches
Mail list logo
