Re: gitSCM failed after updates

2019-09-29 Thread 'Henry Xu' via Jenkins Users
Hi, thanks for your suggestion. I downgrade the git from 2.21.0 to 2.17.1 
(the version I used on the old machine) and anything work fine. I am 
wondering why the git version may cause issue of this kind.

On Monday, September 30, 2019 at 8:01:52 AM UTC+8, Mark Waite wrote:
>
>
>
> On Sun, Sep 29, 2019 at 5:12 PM Henry Xu  wrote:
>
>> I guess I have same issue. And it's wired as it works will on a machine I 
>> provisioned a year ago. Can you kindly provide more detail about how to 
>> using Global Tool Configuration to fix this problem? Thanks in advance.
>>
>>
> The Jenkins global tool configuration won't fix the problem, at least as 
> far as I know.
>
> If you have the same problem, then you are running Windows, have installed 
> cygwin, and have configured Jenkins to use the git program that is 
> available with cygwin.  The solution is to install git for Windows and 
> assure that it is the program which is used by Jenkins, instead of the git 
> program that is available with cygwin.  The Jenkins git plugin does not 
> test with the command line git version that is included with cygwin.  It 
> tests with git for Windows.
>
> Another alternative (for many use cases) is to enable JGit as a git 
> implementation in your Jenkins server, then configure the job to use JGit 
> instead of command line git.  JGit is able to run most use cases, but not 
> all use cases that are supported by command line git.  Refer to 
> https://plugins.jenkins.io/git-client for instructions to enable JGit in 
> your installation.
>  
>
>>
>> Caused by: hudson.plugins.git.GitException: Command "git fetch --tags 
>> --force --progress xxx +refs/heads/*:refs/remotes/Fiji/* --prune" returned 
>> status code 128:
>> stdout: 
>> stderr: error: cannot run c:\jws2\workspace\xxx\ssh7984855687134194056.bat: 
>> No such file or directory
>> fatal: unable to fork
>>
>>  at 
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042)
>>  at 
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761)
>>  at 
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72)
>>  at 
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442)
>>  at 
>> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
>>  at 
>> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
>>  at hudson.remoting.UserRequest.perform(UserRequest.java:212)
>>  at hudson.remoting.UserRequest.perform(UserRequest.java:54)
>>  at hudson.remoting.Request$2.run(Request.java:369)
>>  at 
>> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
>>  at java.util.concurrent.FutureTask.run(Unknown Source)
>>  at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>>  at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>>  at java.lang.Thread.run(Unknown Source)
>>  Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to 
>> SDET-XMN160
>>  at 
>> hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743)
>>  at 
>> hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
>>  at hudson.remoting.Channel.call(Channel.java:957)
>>  at 
>> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)
>>  at sun.reflect.GeneratedMethodAccessor709.invoke(Unknown Source)
>>  at 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>  at java.lang.reflect.Method.invoke(Method.java:498)
>>  at 
>> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)
>>  at com.sun.proxy.$Proxy109.execute(Unknown Source)
>>  at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:892)
>>  at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1161)
>>  at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192)
>>  at 
>> org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120)
>>  at 
>> org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90)
>>  at 
>> org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77)
>>  at 
>> org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
>>  at 
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>>  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>  at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>>  at 
>> 

Re: gitSCM failed after updates

2019-09-29 Thread 'Henry Xu' via Jenkins Users
I guess I have same issue. And it's wired as it works will on a machine I 
provisioned a year ago. Can you kindly provide more detail about how to 
using Global Tool Configuration to fix this problem? Thanks in advance.


Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --force 
--progress xxx +refs/heads/*:refs/remotes/Fiji/* --prune" returned status code 
128:
stdout: 
stderr: error: cannot run c:\jws2\workspace\xxx\ssh7984855687134194056.bat: No 
such file or directory
fatal: unable to fork

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
at hudson.remoting.UserRequest.perform(UserRequest.java:212)
at hudson.remoting.UserRequest.perform(UserRequest.java:54)
at hudson.remoting.Request$2.run(Request.java:369)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to 
SDET-XMN160
at 
hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743)
at 
hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
at hudson.remoting.Channel.call(Channel.java:957)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146)
at sun.reflect.GeneratedMethodAccessor709.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132)
at com.sun.proxy.$Proxy109.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:892)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1161)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1192)
at 
org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120)
at 
org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90)
at 
org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77)
at 
org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)


On Wednesday, June 12, 2019 at 5:09:22 AM UTC+8, Giles wrote:
>
> Nailed it in one.
>
> I was sure it was a Jenkins issue ... but I'd upgraded Cygwin at the same 
> time, and that probably included their version of git.  Which yes, is my 
> default git.  I changed "Manage Jenkins" -> "Global Tool Configuration" -> 
> git to the just-installed "Git for Windows", and ... fixed.  I may have to 
> make some changes in the Jenkinsfiles themselves, but it seems clear now 
> that the latest Cygwin git broke something, and that Git for Windows fixed 
> it ...
>
> This was crisis-level breakage for my department - I can't thank you 
> enough.
>
> On Tuesday, 11 June 2019 16:36:38 UTC-4, Mark Waite wrote:
>>
>> Are you quite sure that your configuration did not change in about the 
>> same time as that upgrade?
>>
>> The log file indicates that you're running command line git as provided 
>> by Cygwin.  Is that intentional?  Has it always been that way?  
>>
>> I don't test the Jenkins git plugin with Cygwin.  I test with Git for 
>> Windows.  I'm glad cygwin git works, but don't intend to apply effort to 
>> make it work.
>>
>> I don't see anything suspicious or troubling in the list of updates.  As 
>> far as I can tell, none of them should have changed