We're on Windows with Git plugin 1.1.17, but no slave - just a single 
Jenkins node.

On Thursday, April 26, 2012 2:42:20 AM UTC-7, Rick Gomes wrote:

> I've been having the same problem, I've read online it has to do with the 
> version of the git plugin installed on Jenkins. Might not be the same 
> problem I'm having but the issue seems to be caused by git plugin version > 
> 1.1.14 and a windows slave machine. Is this the same setup you're using? 
>
> Rick
>
> On Wednesday, April 25, 2012 5:34:07 PM UTC+1, dwalling wrote: 
>>
>> Two more bits of information that might be relevant:
>> 1. Git 1.7.10 was installed into C:\Git
>> 2. In the Jenkins system configuration page, the path to Git is specified 
>> as C:\Git\cmd\git.cmd. I tried specifying the path as C:\Git\bin\git.exe, 
>> but in that case git.exe spawns ssh.exe which hangs. I can use the Git bash 
>> shell and get the repository just fine though without specifying a 
>> password (currently the ssh key has no password)
>>  
>> Don
>>  
>>
>> On Wednesday, April 25, 2012 8:05:20 AM UTC-7, dwalling wrote:
>>
>>> I've attached the config file. I did edit it in 2 spots prior to posting 
>>> - where it has "internalgithubserver" is normally an actual hostname for an 
>>> internal server. To answer your questions:
>>> 1. No, we don't currently use the delete workspace plugin. I have 
>>> manually deleted the workspace while trying to figure this out, but it 
>>> hasn't changed the symptoms. 
>>> 2. Yes, this Jenkins is on windows, with msysgit 1.7.10 installed. We 
>>> don't currently use a wrapper script. If you think that's worth a try, is 
>>> there an example somewhere?
>>>  
>>> If this info isn't clarifying, I'll try to set up a debug Jenkins and do 
>>> some code-level investigation. Probably won't happen until the weekend or 
>>> later, though...
>>> Thanks,
>>> Don
>>>  
>>>  
>>>
>>> On Tuesday, April 24, 2012 12:35:54 PM UTC-7, sti wrote:
>>>
>>>> Your problem is really puzzling... I think I have seen that before but
>>>> now I cannot remember what was the solution. Would it be possible to
>>>> see the job configuration, the config.xml file? 
>>>>
>>>> If not, here are some shots in the dark: 
>>>>
>>>> Do you use Delete Workspace plugin to delete workspace after the build? 
>>>>
>>>> Do you run Jenkins on Windows? Does Jenkins call git.exe directly or
>>>> do you have a wrapper script for it? 
>>>>
>>>> -- Sami 
>>>>
>>>> 2012/4/24 dwalling <dwall...@adobe.com>:
>>>> > yes, leaving it blank and letting it default to ** works just fine for
>>>> > snapshot builds. Then when I attempt to do a release build it 
>>>> complains of a
>>>> > detached head. I suppose I can add pre-steps to the build to do the 
>>>> correct
>>>> > git commands to make this work, but didn't think I'd need to do that. 
>>>> We're
>>>> > switching from perforce to git, and I assumed the build steps would be
>>>> > similar... perhaps not..
>>>> > Don
>>>> >
>>>> >
>>>> > 07:55:26  Caused by: org.apache.maven.scm.ScmException: Detecting the
>>>> > current branch failed: fatal: ref HEAD is not a symbolic ref
>>>> >
>>>> > 07:55:26
>>>> >
>>>> > 07:55:26          at
>>>> > 
>>>> org.apache.maven.scm.provider.git.gitexe.command.branch.GitBranchCommand.getCurrentBranch(GitBranchCommand.java:144)
>>>> >
>>>> > 07:55:26          at
>>>> > 
>>>> org.apache.maven.scm.provider.git.gitexe.command.checkin.GitCheckInCommand.createPushCommandLine(GitCheckInCommand.java:185)
>>>> >
>>>> > 07:55:26          at
>>>> > 
>>>> org.apache.maven.scm.provider.git.gitexe.command.checkin.GitCheckInCommand.executeCheckInCommand(GitCheckInCommand.java:125)
>>>> >
>>>> > 07:55:26          at
>>>> > 
>>>> org.apache.maven.scm.command.checkin.AbstractCheckInCommand.executeCommand(AbstractCheckInCommand.java:53)
>>>> >
>>>> > 07:55:26          at
>>>> > 
>>>> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
>>>> >
>>>> > 07:55:26          ... 39 more
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > On Monday, April 23, 2012 11:27:29 PM UTC-7, 
>>>> sebasti...@softwareag.com
>>>> > wrote:
>>>> >>
>>>> >> > -----Original Message-----
>>>> >> > From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
>>>> >> > us...@googlegroups.com] On Behalf Of dwalling
>>>> >> > Sent: Dienstag, 24. April 2012 01:45
>>>> >> > To: jenkinsci-users@googlegroups.com
>>>> >> > Subject: Re: how to build a specific git branch with jenkins
>>>> >> >
>>>> >> > Jenkins console output is below (except that I've replaced actual 
>>>> host
>>>> >> > names with dummy values. The error appears whether I use 
>>>> origin/master
>>>> >> > or just master in the branch specifier field (instead of the **)
>>>> >>
>>>> >> Does it work if you don't specify a branch and keep **?
>>>> >>
>>>> >> Sebastian
>>>> >>
>>>> >> Software AG – Group Executive Board: Karl-Heinz Streibich
>>>> >> (Vorsitzender/Chairman), Arnd Zinnhardt, Mark Edwards, Dr. Wolfram 
>>>> Jost,
>>>> >> Kamyar Niroumand, Paul Orme-Smith, Darren Roos, Ivo Totev
>>>> >>
>>>> >> Sitz/Registered office: Uhlandstraße 12, 64297 Darmstadt, Germany –
>>>> >> Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/
>>>> >> Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Dr. 
>>>> Wolfram
>>>> >> Jost, Arnd Zinnhardt; - Aufsichtsratsvorsitzender/ Chairman of the
>>>> >> Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com
>>>> >>
>>>> >
>>>>
>>>>     

Reply via email to