def recipients = emailextrecipients([developers()])
--
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-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/de0f53c9-9512-4fd6-a258-e604412ff77a%40googlegroups.com.
You can turn on debug mode in the global config for Email Ext. The code isn't really doing anything major, it just looks at the changesets and get the authors, so I am not sure why it would be taking that long.
On Fri, Apr 24, 2020 at 1:59 PM Sverre Moe <sver...@gmail.com> wrote:
Calling the pipeline step emailextrecipients when there are changes takes too much time.--
A normal git checkout that takes 10-15 seconds, will usually take 1-2 minutes when there are changes, just because of emailextrecipients.
All I want is the authors from the current build changes. I see no reason why this should take so long.
I took a small look at the code for emailextrecipients, and it seems it looks also on previous builds.
def recipients = emailextrecipients([developers()])Our developers want the builds to run as fast as it can. Time is precious.
I am considering removing this recipients. I already have the git repository maintainers I can send email notifications to if anything goes wrong.The backside of removing this, is I cannot send email notifications for the developers, just the maintainers (and those only want notifications for release build, and not all continuous builds).
The reason I call emailextrecipients during the Checkout stage, is because that is the only stage where I have access to the git repository. Later in the build if it fails I do not have access to git anymore.The emailextrecipients code does have some Debug logging. How can I enable this to see what it is actually doing?
I was thinking of implementing my own parsing of the change records. It cannot possibly take more than a few seconds to find the authors of all the changes.
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 jenkins...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/de0f53c9-9512-4fd6-a258-e604412ff77a%40googlegroups.com.
--Website: http://earl-of-code.com
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/fbf04c99-b61b-4109-ac21-50a77fca08c0%40googlegroups.com.
[Pipeline] emailextrecipients Collecting change authors... build: 168 adding author: Sverre MoeAdding Sverre Moe with address sve...@company.com Analyzing: sve...@company.com Looking for: sve...@company.com starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: sve...@company.com => found type: 0 Analyzing: sve...@company.com Looking for: sve...@company.com starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: sve...@company.com => found type: 0 Analyzing: sve...@company.com Looking for: sve...@company.com starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: sve...@company.com => found type: 0
I think the debug logs will just go to the build log.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/fbf04c99-b61b-4109-ac21-50a77fca08c0%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d96643c8-b4d1-46bc-9339-c5094dd2d3c7%40googlegroups.com.
Can you add timestamps? It's hard to tell from what you posted when things are occurring.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d96643c8-b4d1-46bc-9339-c5094dd2d3c7%40googlegroups.com.
Can you add timestamps? It's hard to tell from what you posted when things are occurring.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d96643c8-b4d1-46bc-9339-c5094dd2d3c7%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6ea53ce0-e5a3-4d62-90a7-47ba43a482a1%40googlegroups.com.
sending email always involves a forward lookup and many mail servers do a reverse lookup on the sender's IP.
---
Jeremy Mordkoff
Director of Engineering Services
RIFT, inc
900 Chelmsford Street, 4th floor, tower 3Lowell, MA 018511.978.257.2183 (cell)
From: jenkins...@googlegroups.com <jenkins...@googlegroups.com> on behalf of Sverre Moe <sver...@gmail.com>
To unsubscribe from this group and all its topics, send an email to jenkins...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c30c15e2-6aa8-4016-a27e-c4711607642b%40googlegroups.com.
Use the timestamps plugin , it has a mode to add global timestamps or you can configure options per pipeline
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6ea53ce0-e5a3-4d62-90a7-47ba43a482a1%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3ea8d7eb-4b22-48ca-9f05-5f7fcc86d0d8%40googlegroups.com.
There is no lookup until the email is sent. There may be a call to resolve a username to the email address though. Are you using ldap or AD?
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3ea8d7eb-4b22-48ca-9f05-5f7fcc86d0d8%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e7aa49cb-cf0a-4fd1-8d52-547e54ea6e6c%40googlegroups.com.
Sorry, I misspoke about this. The email-ext plugin uses ChangeSet.Entry.getAuthor(), depending on the SCM plugin you are using, it can do lookups like I mentioned. The Git plugin will try and do the resolution of username -> email using the mail resolver from the Mailer plugin (which is where the extension point lives). I was confusing where the resolver was in the infrastructure. The TL;DR is that it is still the MailResolver feature that is taking the time, but the sequence was different than I remembered.
On Mon, Apr 27, 2020 at 10:42 AM Slide <slid...@gmail.com> wrote:
That sounds like the culprit to me. Email-ext has to resolve usernames from the changeset so an email address. It provides an extension point for this that other plugins can implement to provide that service. If you are having long delays accessing LDAP, that would definitely point to that as a culprit for the length of time.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e7aa49cb-cf0a-4fd1-8d52-547e54ea6e6c%40googlegroups.com.
--Website: http://earl-of-code.com--Website: http://earl-of-code.com
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1b23d07c-39c0-4546-9875-c7e0e711f09b%40googlegroups.com.
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 in our company a single badly configured server tool doing too many LDAP requests managed to led to quite interesting follow-up failure symptoms for other systems…)
HTH Reinhold
.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVe_XW3tZcGy%2B4XV78o5OtGGxJ_BuH-xYieZU0x-WH5D%2BQ%40mail.gmail.com.
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 in our company a single badly configured server tool doing too many LDAP requests managed to led to quite interesting follow-up failure symptoms for other systems…)
HTH Reinhold
From: jenkins...@googlegroups.com <jenkins...@googlegroups.com> On Behalf Of Slide
Sent: Dienstag, 28. April 2020 17:07
To: Jenkins User Mailing List <jenkins...@googlegroups.com>
Subject: 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?
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit
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 guess that email-ext insider Slide might have much better hints…
HTH Reinhold
From: jenkins...@googlegroups.com <jenkins...@googlegroups.com>
On Behalf Of Sverre Moe
Sent: Mittwoch, 29. April 2020 10:44
To: Jenkins Users <jenkins...@googlegroups.com>
Subject: Re: The pipeline emailextrecipients step takes too long time
This had no or very little impact on the time used by emailextrecipient.
--
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-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/172bfdd6-f04e-4011-b0c0-5062585c80a2%40googlegroups.com.
def getAuthors(build) {
final def authors = []
final def changeSets = build.changeSets
for (def cs: changeSets) {
final def author = cs.getAuthorEmail()
authors.add(author)
}
return authors.join(" ")
}
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit
def getAuthors(build) {
final def authors = []
final def changeSets = build.changeSets
for (def cs: changeSets) {
final def author = cs.getAuthorEmail()
authors.add(author)
}
return authors.join(" ")
}
--
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-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c6fa5643-4330-4b4f-a59f-0216f9f214f9%40googlegroups.com.
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 <sver...@gmail.com> wrote:
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 author = cs.getAuthorEmail()
authors.add(author)
}
return authors.join(" ")
}Though it would preffer to use emailextrecipients, because it can do so much more. Not just developers, but culprits, etc.The emailextrecipient could use an configuration option to retrieve the AuthorEmail instead directly, no lookup/resolve needed.
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 jenkins...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c6fa5643-4330-4b4f-a59f-0216f9f214f9%40googlegroups.com.
--Website: http://earl-of-code.com
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5691f5d0-dae8-4452-bf7e-3993f5df17fd%40googlegroups.com.