09:35
To: Jenkins Users
Subject: Re: setup of Jenkins infrastructure
Thanks so much Dirk.
I will convince for Linux Jenkins master.
Burden meaning - if 3000+ Jenkins jobs are created then
even though jobs run @ slaves
but respective build information will be stored @ Jenkins master. Hence it is
Very much grateful to your feedback Dirk.
Thanks a lot.
On Thursday, March 1, 2018 at 2:23:57 PM UTC+5:30, Dirk Heinrichs wrote:
> Hi,
>
> > Burden meaning - if 3000+ Jenkins jobs are created then
> > even though jobs run @ slaves
> > but respective build information will be stored @ Jenkins
Hi,
> Burden meaning - if 3000+ Jenkins jobs are created then
> even though jobs run @ slaves
> but respective build information will be stored @ Jenkins master. Hence it is
> seeing as burden.
We've got approx. 1000 jobs, and don't experience any problems on the master
(VM with 4 vCPU and 16G
Thanks so much Dirk.
I will convince for Linux Jenkins master.
Burden meaning - if 3000+ Jenkins jobs are created then
even though jobs run @ slaves
but respective build information will be stored @ Jenkins master. Hence it
is seeing as burden.
What would you suggest - if Jenkins page load is d
Hi,
> My Plan is
> 1. Create Jenkins master in in windows VM (Provided 16GB RAM)
We were also running our Jenkins master on Windows for the past couple of
years, but we finally migrated it to Linux last year. Windows really (still)
doesn't make a good server OS (even though it has "Server" in
Hi ,
I'm preparing topology of new setup of Jenkins infrastructure. We will be
given 60 Virtual VMs (Consists of 45 Windows + 15 Linux VMs)
*Target :*
Need to submit the high level topology for the jenkins infrastructure for
Test Automation and Generation of reports.
*My Plan is*
1. C
