Re: HTML message rejected: Re: Distribute continuous integration (build) to servers outside docker container

Dear Fuego users,

I have a requirement, so I thought of checking with the community if
it was feasible and if so what is the best or most efficient way to
implement it.
We have fuego setup in a server and all our continuous integration
jobs (for multiple code bases) are setup in it. But the issue is there
are too many builds happening, which puts pressure on the hard disk
(so many read/writes) and also increases the docker container size
(because of build logs).

Hence I would like to know if we can distribute the load to another
server, for e.g. job will be created on our main server but build will
happen on the agent on another server. The idea is to move out all
cpu, memory, storage intensive activity to agents (other servers) on
the network. The resultant logs can also be stored on those servers
(outside docker container) so that docker size won't be growing
rapidly.

I tried creating a new node and setup an agent (connect via ssh) but
facing issues in installing the 'SSH Build Agents' plugin because of
compatibility issues (jenkins version needs to be upgraded).

If anyone already tried and has a solution for this issue please let me kno=
w.

Also, what is the best way to backup the container after trimming it
down (remove unwanted files/logs etc. and reduce it's size)?

Regards,
Dhinakar K.
Samsung India, Bengaluru.


On Thu, Feb 1, 2024 at 11:52=E2=80=AFPM <[email protected]> wrote=
:
>
> Greetings!
>
> This is the mlmmj program managing the <[email protected]> mailing
> list.
>
> Your message to <[email protected]> was not delivered to the list
> because it contained a HTML part. Only text/plain messages are allowed on
> this list.
>
> Please configure your mail client to only send plain text mail.
>
> For your reference, the rejected message follows below.
>
>
>
> ---------- Forwarded message ----------
> From: dhinakar k <[email protected]>
> To: [email protected], [email protected], "Bird, T=
imothy" <[email protected]>
> Cc:
> Bcc:
> Date: Thu, 1 Feb 2024 23:51:30 +0530
> Subject: Re: Distribute continuous integration (build) to servers outside=
 docker container
> Dear Fuego users,
>
> I have a requirement, so I thought of checking with the community if it w=
as feasible and if so what is the best or most efficient way to implement i=
t.
> We have fuego setup in a server and all our continuous integration jobs (=
for multiple code bases) are setup in it. But the issue is there are too ma=
ny builds happening, which puts pressure on the hard disk (so many read/wri=
tes) and also increases the docker container size (because of build logs).
>
> Hence I would like to know if we can distribute the load to another serve=
r, for e.g. job will be created on our main server but build will happen on=
 the agent on another server. The idea is to move out all cpu, memory, stor=
age intensive activity to agents (other servers) on the network. The result=
ant logs can also be stored on those servers (outside docker container) so =
that docker size won't be growing rapidly.
>
> I tried creating a new node and setup an agent (connect via ssh) but faci=
ng issues in installing the 'SSH Build Agents' plugin because of compatibil=
ity issues (jenkins version needs to be upgraded).
>
> If anyone already tried and has a solution for this issue please let me k=
now.
>
> Also, what is the best way to backup the container after trimming it down=
 (remove unwanted files/logs etc. and reduce it's size)?
>
> Regards,
> Dhinakar K.
> Samsung India, Bengaluru.
>
> On Thu, Feb 1, 2024 at 10:30=E2=80=AFPM dhinakar k <[email protected]>=
 wrote:
>>
>> Dear Fuego users,
>>
>> I have a requirement, so I thought of checking with the community if it =
was feasible and if so what is the best or most efficient way to implement =
it.
>> We have fuego setup in a server and all our continuous integration jobs =
(for multiple code bases) are setup in it. But the issue is there are too m=
any builds happening, which puts pressure on the hard disk (so many read/wr=
ites) and also increases the docker container size (because of build logs).
>>
>> Hence I would like to know if we can distribute the load to another serv=
er, for e.g. job will be created on our main server but build will happen o=
n the agent on another server. The idea is to move out all cpu, memory, sto=
rage intensive activity to agents (other servers) on the network. The resul=
tant logs can also be stored on those servers (outside docker container) so=
 that docker size won't be growing rapidly.
>>
>> I tried creating a new node and setup an agent (connect via ssh) but fac=
ing issues in installing the 'SSH Build Agents' plugin because of compatibi=
lity issues (jenkins version needs to be upgraded).
>>
>> If anyone already tried and has a solution for this issue please let me =
know.
>>
>> Also, what is the best way to backup the container after trimming it dow=
n (remove unwanted files/logs etc. and reduce it's size)?
>>
>> Regards,
>> Dhinakar K.
>> Samsung India, Bengaluru.