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 RAM). We also use the "Archive Artifact" plugin a lot,
which stores to-be-kept artifacts on the master for later retrieval. Some of
those artifacts are sized ~3G.
> What would you suggest - if Jenkins page load is damn slow ?
A general mistake we made was to put all the jobs into the main page. It was
just lately that we discovered the wonders of the Folder plugin and started to
use it to organize our jobs. Views also help here, but I - personally - like
the folders more.
Bye...
Dirk
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/BN7PR15MB24011BF311BC16E6FEC26004AAC60%40BN7PR15MB2401.namprd15.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.
