Scaling question - 1500 jobs a night?

Hiya, Clear question up front: what additional concerns should I have when running 1500 jobs a night? Details: We are using Jenkins to run integration tests for our software. I wrote a pipeline script to operate on a single chunk of data representing a test case. However, I have roughly

Re: The pipeline emailextrecipients step takes too long time

How would emails get to the correct user if their email address can't be resolved from the username? I don't know of a way to disable the username -> email resolution. Did you try changing the search criteria for the LDAP plugin as related in one of your other posts? On Tue, Apr 28, 2020 at 4:58

RE: The pipeline emailextrecipients step takes too long time

Sorry for the following potentially too naïve hint: In addition try to also play around with the LDAP caching, if not yet activated – because that may also reduce load on LDAP server (in case that is a problem); of course, other LDAP clients in your company should do the same! (I remember that

Re: persistentVolumeClaimWorkspaceVolume produced emptyDir volume instead of PVC

Hmm, I lost the correct indentation in the message, but the yaml indentation is correct in my project. On Tuesday, April 28, 2020 at 2:56:40 PM UTC-4, David Warburton wrote: > > Hi mailing list, > > I'm building a pipeline for neural net training that needs to operate on > around 650G of data

persistentVolumeClaimWorkspaceVolume produced emptyDir volume instead of PVC

Hi mailing list, I'm building a pipeline for neural net training that needs to operate on around 650G of data using the kubernetes plugin to run agents in pods. In between builds I'd like the data to stick around in a persistent volume for the workspace. It seems like the

Re: The pipeline emailextrecipients step takes too long time

The LDAP Search criteria: Not sure how the search criterias could be changed. User search base: ou=users User search filter: sAMAccountName={0} Found this setting in Configure Global Security for LDAP: Disable Ldap Email Resolver I ticked it, now I will see if that can help the issue. LDAP

Re: [EVENT]: Calling for Jenkins submissions

Hi All, The Call for proposal for DevOps World has been extended to May 18. If you haven't submitted your Jenkins and or CI CD talk, you now have until May 18 to submit. https://www.cloudbees.com/devops-world/call-for-presentations

Re: The pipeline emailextrecipients step takes too long time

Any idea how to workaround this? Any way to disable the resolving of email adresses? Using Git SCM checkout in Pipeline /Sverre mandag 27. april 2020 21.16.25 UTC+2 skrev slide følgende: > > Sorry, I misspoke about this. The email-ext plugin uses > ChangeSet.Entry.getAuthor(), depending on the