Re: Groovy script to cancle jobs from queue

Were you able to find a solution for this. I encountered something similar where I have many jobs in queue with different parameter values and I wanted to cancel the job where the job name and parameter value matches. def q = Jenkins.instance.queue q.items.each { if((it.task.name == job_name_

Re: The pipeline emailextrecipients step takes too long time

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 e

Re: The pipeline emailextrecipients step takes too long time

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 cul

Re: The pipeline emailextrecipients step takes too long time

Our Jenkins have enabled Login with LDAP. We do occasionally experience LDAP timeout also. 60 seconds timeout. Perhaps there is a relation to that, considering that each author found by emailextrecipients also takes 60 seconds each. mandag 27. april 2020 16.25.37 UTC+2 skrev slide følgende: > >

Re: The pipeline emailextrecipients step takes too long time

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? On Mon, Apr 27, 2020, 01:39 Sverre Moe wrote: > Well at this point I am not sending any email, yet. > I am looking up recipients from change set, so I can

Re: The pipeline emailextrecipients step takes too long time

It seems emailextrecipients are using 60 seconds for each email it finds. I am going to add the timestamper plugin to see what parts of the debug output from emailextrecipients are taking so long. mandag 27. april 2020 10.39.30 UTC+2 skrev Sverre Moe følgende: > > Well at this point I am not sen

Re: python script not executing in "execute python script" step

Hi, this looks like there is no python in the path on the agent running the job. The "Execute python" step will not magically supply a python installation. Björn -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this grou

python script not executing in "execute python script" step

this is error i got Started by user fwqe Running as SYSTEM Building in workspace C:\Program Files (x86)\Jenkins\workspace\Test [Test] $ python C:\WINDOWS\TEMP\jenkins6513206815000733591.py The system cannot find the file specified FATAL: command execution faile

cannot run python script in jenkins ui

the attached file config below is error i got when built Running as SYSTEM Building in workspace C:\Program Files (x86)\Jenkins\workspace\Test [Test] $ python C:\WINDOWS\TEMP\jenkins6513206815000733591.py The system cannot find the file specified FATAL: command execution failed java.io.IOExcepti

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

Well at this point I am not sending any email, yet. I am looking up recipients from change set, so I can use that later when/if I send email for failed builds. Does emailextrecipients do the lookup itself, or is it done when calling mail step? mandag 27. april 2020 01.12.48 UTC+2 skrev Jeremy M