Re: The pipeline emailextrecipients step takes too long time

Some scm providers can map usernames to emails directly. So, it doesn't require AD or LDAP for email resolution. In the end, if none of the resolvers returns a valid response, then the default domain is appended to the username and that is used. On Thu, Apr 30, 2020, 12:42 Sverre Moe wrote: > I

Re: The pipeline emailextrecipients step takes too long time

I see that getAuthorEmail is only part of the GitChangeSet not its super ChangeSet.Entry. Seems better to get the Email rather the Name and then do lookup. The commit has both Name and Email, both should belong in the ChangeSet API. What does it do if you don't have AD or LDAP on Jenkins, then t

Re: The pipeline emailextrecipients step takes too long time

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. >

Re: The pipeline emailextrecipients step takes too long time

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 autho

Re: The pipeline emailextrecipients step takes too long time

ttwoch, 29. April 2020 10:44 > *To:* Jenkins Users > > *Subject:* Re: The pipeline emailextrecipients step takes too long time > > > > This had no or very little impact on the time used by emailextrecipient. > > > > Disbled email resolver against LDAP > >

RE: The pipeline emailextrecipients step takes too long time

ns? But I guess that email-ext insider Slide might have much better hints… HTH Reinhold From: jenkinsci-users@googlegroups.com On Behalf Of Sverre Moe Sent: Mittwoch, 29. April 2020 10:44 To: Jenkins Users Subject: Re: The pipeline emailextrecipients step takes too long time This had no or v

Re: The pipeline emailextrecipients step takes too long time

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 s

Re: The pipeline emailextrecipients step takes too long time

s.com > *On Behalf Of *Slide > *Sent:* Dienstag, 28. April 2020 17:07 > *To:* Jenkins User Mailing List > > > *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 &

RE: The pipeline emailextrecipients step takes too long time

Mailing List 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 cri

Re: The pipeline emailextrecipients step takes too long time

gt;>>> sending email always involves a forward lookup and many mail servers >>>>>>> do a reverse lookup on the sender's IP. >>>>>>> >>>>>>> >>>>>>> >>>>>>> *--- Jeremy Mordkoff* >&

Re: The pipeline emailextrecipients step takes too long time

t; >>>>>> >>>>>> *--- Jeremy Mordkoff* >>>>>> Director of Engineering Services >>>>>> <https://www.riftio.com> >>>>>> RIFT, inc >>>>>> 900 Chelmsford Street, 4th floor, tower 3 &

Re: The pipeline emailextrecipients step takes too long time

>>>> <https://www.riftio.com> >>>>> RIFT, inc >>>>> 900 Chelmsford Street, 4th floor, tower 3 >>>>> Lowell, MA 01851 >>>>> 1.978.257.2183 (*cell*) >>>>> <http://www.riftio.com>www.riftio.com

Re: The pipeline emailextrecipients step takes too long time

th floor, tower 3 >>>> Lowell, MA 01851 >>>> 1.978.257.2183 (*cell*) >>>> <http://www.riftio.com>www.riftio.com >>>> -- >>>> *From:* jenkins...@googlegroups.com on >>>> behalf of Sverre Moe >&g

Re: The pipeline emailextrecipients step takes too long time

>>> <https://www.riftio.com> >>> RIFT, inc >>> 900 Chelmsford Street, 4th floor, tower 3 >>> Lowell, MA 01851 >>> 1.978.257.2183 (*cell*) >>> <http://www.riftio.com>www.riftio.com >>> ---------- >>

Re: The pipeline emailextrecipients step takes too long time

loor, tower 3 >> Lowell, MA 01851 >> 1.978.257.2183 (*cell*) >> <http://www.riftio.com>www.riftio.com >> -- >> *From:* jenkins...@googlegroups.com on >> behalf of Sverre Moe >> *Sent:* Sunday, April 26, 2020 3:32 PM >> *To:* Jenkins

Re: The pipeline emailextrecipients step takes too long time

iftio.com> >> RIFT, inc >> 900 Chelmsford Street, 4th floor, tower 3 >> Lowell, MA 01851 >> 1.978.257.2183 (*cell*) >> <http://www.riftio.com>www.riftio.com >> -- >> *From:* jenkins...@googlegroups.com on >> behalf

Re: The pipeline emailextrecipients step takes too long time

This plugin you are mentioning? https://plugins.jenkins.io/timestamper/ mandag 27. april 2020 00.30.33 UTC+2 skrev Jan Monterrubio følgende: > > Use the timestamps plugin , it has a mode to add global timestamps or you > can configure options per pipeline > > On Sun, Apr 26, 2020 at 14:32 Sverre

Re: The pipeline emailextrecipients step takes too long time

om > > *Sent:* Sunday, April 26, 2020 3:32 PM > *To:* Jenkins Users > > *Subject:* Re: The pipeline emailextrecipients step takes too long time > > How so? > > Does emailextrecipient do a DNS lookup on each author it can find? > > søndag 26. april 2020 20.12.03

Re: The pipeline emailextrecipients step takes too long time

Lowell, MA 01851 1.978.257.2183 (cell) <http://www.riftio.com>www.riftio.com<http://www.riftio.com> From: jenkinsci-users@googlegroups.com on behalf of Sverre Moe Sent: Sunday, April 26, 2020 3:32 PM To: Jenkins Users Subject: Re: The pipeline emaile

Re: The pipeline emailextrecipients step takes too long time

Use the timestamps plugin , it has a mode to add global timestamps or you can configure options per pipeline On Sun, Apr 26, 2020 at 14:32 Sverre Moe wrote: > How can I add timestamp to the debug output? > > søndag 26. april 2020 18.30.59 UTC+2 skrev slide følgende: >> >> Can you add timestamps?

Re: The pipeline emailextrecipients step takes too long time

How so? Does emailextrecipient do a DNS lookup on each author it can find? søndag 26. april 2020 20.12.03 UTC+2 skrev jeremy mordkoff følgende: > > check that DNS is working. I've seen huge delays on basic ops when DNS > lookups are timing out. Check forward and reverse lookups. > > > > On Sund

Re: The pipeline emailextrecipients step takes too long time

How can I add timestamp to the debug output? søndag 26. april 2020 18.30.59 UTC+2 skrev slide følgende: > > Can you add timestamps? It's hard to tell from what you posted when things > are occurring. > > On Sun, Apr 26, 2020, 01:16 Sverre Moe > > wrote: > >> Yes it did. >> >> Just one simple lit

Re: The pipeline emailextrecipients step takes too long time

check that DNS is working. I've seen huge delays on basic ops when DNS lookups are timing out. Check forward and reverse lookups. On Sunday, April 26, 2020 at 12:30:59 PM UTC-4, slide wrote: > > Can you add timestamps? It's hard to tell from what you posted when things > are occurring. > > On

Re: The pipeline emailextrecipients step takes too long time

Can you add timestamps? It's hard to tell from what you posted when things are occurring. On Sun, Apr 26, 2020, 01:16 Sverre Moe wrote: > Yes it did. > > Just one simple little commit, and Checkout took a little over 1 minute > > [Pipeline] emailextrecipients >

Re: The pipeline emailextrecipients step takes too long time

I added println how much time it used. Mostly it uses only a few milliseconds. In one case so far, It used a little over 6 milliseconds. The output from the emailextrecipients debug was no different from those build that only took a few milliseconds. søndag 26. april 2020 10.15.51 UTC+2 skre

Re: The pipeline emailextrecipients step takes too long time

Yes it did. Just one simple little commit, and Checkout took a little over 1 minute [Pipeline] emailextrecipients Collecting change authors... build: 168 adding author:

Re: The pipeline emailextrecipients step takes too long time

I think the debug logs will just go to the build log. On Sat, Apr 25, 2020, 11:58 Sverre Moe wrote: > Tried to configure debug > Manage Jenkins > Configure System > Extended Email Notification >Enable > Debug > > I added a System Log for "hudson.plugins.emailext" and Log Level ALL. > > Hope I ca

Re: The pipeline emailextrecipients step takes too long time

Tried to configure debug Manage Jenkins > Configure System > Extended Email Notification >Enable Debug I added a System Log for "hudson.plugins.emailext" and Log Level ALL. Hope I can find something about why it takes so long. fredag 24. april 2020 23.20.40 UTC+2 skrev slide følgende: > > You c

Re: The pipeline emailextrecipients step takes too long time

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 wrote: > Calling the pipeline step emailex