Ugh, I saw your request in two different mailing lists for the same
information. This list is the correct location for your question. As
Gavin noted in the other list, that list is not the correct location.
Good luck with your search, please don't post duplicate questions into
multiple lists.
You're asking in the wrong location. This mailing list is used for
conversations about the creation and maintenance of the Jenkins
documentation. You want the Jenkins users mailing list or the Jenkins
gitter channels. Refer to https://www.jenkins.io/chat/ for chat channels
and to
Hi All,
Please help me out by providing your suggestion , i have this requirement
very urgent :
is there any way we can stop jenkin job if there is any security
“Critical” or “High” vulnerabilities in the Github repo
is there any way we can achieve this .
Thanks
Ravindra
--
You
Hi,
We are automating the update of our Jenkins instance, and in the last update we
have seen some errors when login into Jenkins: "Some plugins could not be
loaded due to unsatisfied dependencies"
Is there a way to programatically check this, so we can add an automatic
validation step after
The only method available via the ChangeSet API is getAuthor(), which
internally does the lookup to make sure the email address is available, so
no, it can't access author email directly.
On Wed, Apr 29, 2020 at 8:18 AM Sverre Moe wrote:
> My code for finding the changeset authors worked fine.
My code for finding the changeset authors worked fine.
If any developers have wrong email address, then so be it.
This solution is much much faster.
def getAuthors(build) {
final def authors = []
final def changeSets = build.changeSets
for (def cs: changeSets) {
final def
The emailextrecipient gets the author by
ChangeSet getAuthor()
This gets the Name of the author. Then I guess it needs to find the email
address.
But how does it do that?
Does it look up the name in LDAP?
What would it do if LDAP was not configured in Jenkins?
It would be so much easier if it
Ad LDAP: we are also using another configuration element, but again, this may
not be kriegs-entscheidend
userSearchBase: "CN=Users"
If you know that it is the emailextrecipients step and it is really that slow,
then you could maybe find the problem when remote debugging into Jenkins?
But I
This had no or very little impact on the time used by emailextrecipient.
Disbled email resolver against LDAP
Enabled LDAP cache
Checked a build that was built in Jenkins after changing these settings.
The emailextrecipients took 98274 milliseconds, almost 2 minutes, for 2
authors in the change
