Re: Getting Jgit exception in a Job that uses native Git

Navigate to *Manage Jenkins* > *Global Tool Configuration* > *Git* > *Git Installations*. If the only installation configured there is *JGit *or *JGit with Apache HTTP client*, that is the answer. The *Git *installation will probably be what you are looking for. On Friday, March 23, 2018 at

Re: GIT_SSH not working on one of my windows slaves

The name of the temporary directory used for the credentials is based on either the workspace folder path (with @tmp appended) or the environment variables %TEMP% or %TMP%. If none of those contain a space character, then that is not the problem. The plugin usually wirtes a message when it

Re: GIT_SSH not working on one of my windows slaves

Jenkins says "using GIT_SSH to set credential" What is it actually putting in GIT_SSH? On Thursday, May 10, 2018 at 2:38:14 PM UTC-4, red 888 wrote: > > also, if this is helpful this is the global git config on both slaves: > > PS C:\Users\Administrator> git config --list >

Re: GIT_SSH not working on one of my windows slaves

also, if this is helpful this is the global git config on both slaves: PS C:\Users\Administrator> git config --list core.symlinks=false core.autocrlf=true core.fscache=true color.diff=auto color.status=auto color.branch=auto color.interactive=true help.format=html rebase.autosquash=true

Re: GIT_SSH not working on one of my windows slaves

hmm what is the "temporary directory" in this context? The jenkins workspace is configured the same on both slaves (just a folder under c:) so no spaces there Another thing i looked at was *c:\Windows\System32\config\systemprofile\.ssh\* and on both slaves that folder just has a know_hosts

Re: GIT_SSH not working on one of my windows slaves

Have you confirmed that the temporary directory on the failing machine does not include any space characters in its path? There is a known problem on Windows that the credential passing technique required by command line git does not allow a space character in the temporary directory path. I

Re: GIT_SSH not working on one of my windows slaves

I can confirm the git ssh key works and has always worked so the creds themselves should not be an issue. git clone fails on both slaves (when run interactively as a logged in user). The windows task that runs the jnlp executes as the SYSTEM account. I also made sure to do git config --system

Re: GIT_SSH not working on one of my windows slaves

Dumped env vars on both nodes right before checkout, i dont see any real differences. Anything env vars specific to GIT_SSH? Also both slaves are running the same windows build too. On Thursday, May 10, 2018 at 1:44:16 PM UTC-4, slide wrote: > > Can you try dumping the environment variables on

Re: GIT_SSH not working on one of my windows slaves

It could be a "happy accident" that it is working on the first agent. When using a command prompt on the first agent, does `git clone` allow you to clone without prompting for remote username or password? When using a command prompt on the second agent, does it behave the same as the first

Re: GIT_SSH not working on one of my windows slaves

Can you try dumping the environment variables on each node and see if there are any differences? On Thu, May 10, 2018 at 10:42 AM red 888 wrote: > Super frustrating because this is working on one of my windows slaves, but > not this one- and I cant find any config

GIT_SSH not working on one of my windows slaves

Super frustrating because this is working on one of my windows slaves, but not this one- and I cant find any config differences. On the working slave I see this: [Pipeline] checkout Cloning the remote Git repository Cloning repository g...@bitbucket.org:myteam/myapp.git > git init

Is there a way to figure out artifactName in jenkins pipeline without specifying it in the Jenkinsfile?

Is there a way to figure out artifactName in jenkins pipeline without specifying it in the Jenkinsfile? -- 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

Re:

What is your version of the plugins? On Thu, May 10, 2018 at 3:14 AM Victor Martinez < victormartinezru...@gmail.com> wrote: > I'm not sure if you can upgrade those plugins but you could give a go and > run a local jenkins instance with the latest version of those plugins and > see whether the

How to get the value of the "Release version" (and others) from "Module Version Configuration" to a comment

Hi We are using jenkins version 2.73.3 on a Linux Redhat OS 7. We have jobs in > which we execute the option Artifactory Release Staging there is a > section called Module > Version Configuration in which there are two variables >

Re:

I'm not sure if you can upgrade those plugins but you could give a go and run a local jenkins instance with the latest version of those plugins and see whether the same behaviour keeps going. Other than that, I don't have any other suggestions. Cheers -- You received this message because you

Re: How to check "Use Groovy Sandbox" programmatically from groovy : EnvironmentVariableContext

Does it help the below answer? - https://groups.google.com/forum/#!searchin/job-dsl-plugin/Use$20Groovy$20Sandbox%7Csort:date/job-dsl-plugin/UiD7ujvEQ-s/HvgRrAiJAwAJ -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this