Re: Parametrized build for E2E testing in different environments

Thanks, works now! I was also reading about the pipeline, and I've found out that it's based upon the old plugin Build Flow , which used to do exactly what I was hoping for: You can pass parameters to jobs, and get the resulting

How to find who installed a Jenkins plugin

Is there a way to find out who and when was the plugin installed ? Especially for all the plugins that are installed in jenkins. -- 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

Re: Problem with Jenkins email extension plugin

I am not super familiar with the AD plugin, so I am not sure why it would be returning null. Maybe you can raise an issue on Jira (when its back up) for that plugin. On Thu, Jun 4, 2020 at 1:04 PM Mario Jauvin wrote: > the user exists and has an email address in the mail attribute. > > On

Re: Problem with Jenkins email extension plugin

the user exists and has an email address in the mail attribute. On Thursday, June 4, 2020 at 2:37:15 PM UTC-4, slide wrote: > > Does your AD implementation put the email address in a non-standard > attribute? Does the user ID exist in the AD and does that user account have > a valid email

Re: Parametrized build for E2E testing in different environments

Go to the Build section of the job config, and add a build step of type "Use builders from another project". Your job will now use all the Build steps configured in the other job you specify there. The configuration you added would use the "Build Environment" settings from the job you

Virtual Box and vagrant installation

I am trying to use my vagrant file in Git and launch vagrant boot/provision in Jenkins I have 2 options 1. Used the Plugins of vagrant & virtual box in jenkins and tried to access vagrant, it is saying no such file or directory.Means do i need to install vagrant and virtual box in Jenkins

Salesforce auth behind the proxy: force:auth:jwt:grant

Hi... I just started in Jenkins and it's a beginner question. I've tried to run a Salesforce job from Jenkins, I got an error when I try to authorize a salesforce org using JWT flow... force:auth:jwt:grant I installed Jenkins server in my PC, it's behind a proxy. Here is my command line

Re: Problem with Jenkins email extension plugin

Does your AD implementation put the email address in a non-standard attribute? Does the user ID exist in the AD and does that user account have a valid email address attribute? On Thu, Jun 4, 2020 at 10:57 AM Mario Jauvin wrote: > I noticed that the error comes from

Jenkins Base ClearCase Issue

Hi all, I setup Jenkins in a build server using Base ClearCase plugin. For every build, plugin runs the following commands ; $ cleartool lsview -cview -s $ cleartool lsview "view_name" Mostly, these commands runs OK but sporadically the command gives the following output; $ cleartool

Re: Problem with Jenkins email extension plugin

I noticed that the error comes from ActiveDirectoryMailAddressResolverImpl in the active_directory plugin. Any suggestion? Is this a problem with the plugin or with the configuration? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To

Re: Problem with Jenkins email extension plugin

I am using the active directory plugin and found out the following debug log output: Resolving e-mail address for "Smith, Jim" ID=abc456 Jun 04, 2020 1:36:42 PM FINE hudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider Login successful: abc456

Re: Jenkins Agent/Slave on Windows Disconnect Issue

I wonder if that is going to help. The ELB timeout is only good enough for the connections between the 1. Client and ELB and 2. ELB and Backend Instance. In this case, only the Jenkins Master is behind the ALB and the connection between is fine! The Windows Agents mentioned here is not part

Re: Parametrized build for E2E testing in different environments

I see thanks! I never really had the chance to look into pipelines, but now the time might have come. Even Multiple SCM is stating : > Deprecated: Users should migrate to > https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin Anyway, back to

Re: Problem with Jenkins email extension plugin

Do you have the LDAP plugin installed and configured? There needs to be a mechanism that the username can be converted to a an email address, this is called a MailAddressResolver ( javadoc.jenkins.io/plugin/mailer/hudson/tasks/MailAddressResolver.html). Several SCM plugins implement a

Re: Parametrized build for E2E testing in different environments

Using Pipeline you would take a different approach, like having a common script in source control that all the jobs could use to accomplish the common task. I'm surprised that the Template plugin is not working for you, however. We're not at the very latest LTS but at 2.204.5, and it works

Re: Parametrized build for E2E testing in different environments

Thanks Eric, I appreciate it. Unfortunately the template plugin seems not be up-to-date. I've just opened a new issue on JIRA, but I'm not really hopeful.. https://issues.jenkins-ci.org/browse/JENKINS-62568 I noticed there seems to be a couple more template plugins, I might give them a try.

Re: Problem with Jenkins email extension plugin

Is there some diagnostics or debugging I can turn on to troubleshoot this? On Thursday, June 4, 2020 at 9:38:14 AM UTC-4, Christoph Fetzer wrote: > > We are reading the mail addresses from ldap. The assignment user from repo > commit user to mail address happens automagically in the background.

Re: Jenkins Agent/Slave on Windows Disconnect Issue

Thanks for the response! I did check the remoting logs; all I see is below Jun 04, 2020 1:57:27 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking Jun 04, 2020 1:57:27 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to :5 Jun 04, 2020 1:57:27 PM

Re: Problem with Jenkins email extension plugin

Obviously the userid and domain have been camouflaged to protect the innocents. On Thursday, June 4, 2020 at 10:06:53 AM UTC-4, Mario Jauvin wrote: > > This is the output in the pipeline job: > > Sending email to: abc...@company.com > > This does not work in our organization. What could be the

Re: Problem with Jenkins email extension plugin

This is the output in the pipeline job: Sending email to: abc...@company.com This does not work in our organization. What could be the problem? On Thursday, June 4, 2020 at 9:38:14 AM UTC-4, Christoph Fetzer wrote: > > We are reading the mail addresses from ldap. The assignment user from repo

Re: Problem with Jenkins email extension plugin

This is what I thought but the automagical functionality requires an incantation because it is not working. Any suggestions? I have updated all plugins and jenkins to their latest most recent version. It still does not work. On Thursday, June 4, 2020 at 9:38:14 AM UTC-4, Christoph Fetzer

Re: Problem with Jenkins email extension plugin

We are reading the mail addresses from ldap. The assignment user from repo commit user to mail address happens automagically in the background. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving

Re: Problem with Jenkins email extension plugin

I had not. I added the domain but our email system does not accept abc...@company.com. One must use firstname.lastn...@company.com. This information is found in active directory or I believe can be retrieved using ldap. Any solutions? On Thursday, June 4, 2020 at 8:58:25 AM UTC-4, slide

Re: Problem with Jenkins email extension plugin

Did you setup the default domain in the global configuration? On Thu, Jun 4, 2020, 05:54 Mario Jauvin wrote: > > I have noticed that when using DevelopersRecipientProvider in the > declarative pipeline, the information returned is the userid and not the > email address. I get the error: > >

Problem with Jenkins email extension plugin

I have noticed that when using DevelopersRecipientProvider in the declarative pipeline, the information returned is the userid and not the email address. I get the error: Error sending to the following INVALID addresses: abc543 abc543 is the user that committed a change. I also noticed that

Make a test result intentionally unstable

Hello! I have a unit test that from time to time deadlocks. To work around that and at least finish the build and collect the results available so far I made use of a timeout in a try and caught the timeout. When this timeout applies now, I get an overall green testrun which is not what I

Re: Jenkins Agent/Slave on Windows Disconnect Issue

have you looked on the agent in the remoting logs ? I've had (and still have) the same issue. Often I see in the remoting logs on the node an error like    "Readerthread killed by OutOfMemoryError  java.lang.OutOfMemoryError:unable to create new native thread  "which btw does not necessarily

Re: Many Freestyle jobs or many Jenkinsfiles?

similar to other users I also have a quite large set of jobs that use the (scripted, not declarative) Groovy pipelines. In my setup I have deliberately chosen to: - store all the Groovy scripts in SCM - have a seperate dedicated repository for all my Groovy scripts; alternative

Re: Warnings Next Generation Plugin: git rev-parse HEAD^{commit} takes a (too) long time

You can disable that part, see https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md#source-code-blames-for-git-projects > Am 04.06.2020 um 08:31