Jason Kushmaul edited a comment on Bug JENKINS-14752

Same issue here. I reproduced this using the latest versions and documented my steps with an empty repo.

Jenkins master
	Linux, CentOS 6.5
	Jenkins ver. 1.588
	Git Plugin 2.2.7
	Git client plugin 1.11.0
Jenkins slave 
	Windows 8.1 Pro
	using jnlp installed as service.
	E:\Jenkins\workspace\TestNewGitBranch>C:\git\cmd\git.exe --version
		git version 1.9.4.msysgit.2
	java -version
		java version "1.7.0_71"
		Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
		Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

  1. Setup a new empty repo on git hosting (gitlab in this case)
    1. Make public
      ssh://g...@builds.me.local/jk/testgitreponewbranch.git
      I can clone it using Jenkin's key on slave, as the user the service is running as.
  2. Setup a new Jenkins job to be built on windows slave.
    1. Restrict to windows node
    2. Set git repo to above url
      ssh://g...@builds.me.local/jk/testgitreponewbranch.git
    3. Set branches to build to
      */release/*
    4. Set poll SCM to
      */1 * * * *
      (so we don't have to wait)
    5. Save
  3. Check Git Polling
    I see (No changes)
    That's good, we haven't pushed anything to a release/* branch yet.
    Just wait.
  4. Next you'll see git polling log hanging:
    	Started on Nov 4, 2014 9:21:00 AM
    	Polling SCM changes on WINDOWS
    	Using strategy: Default
    	 > "C:\git\cmd\git.exe" rev-parse --is-inside-work-tree # timeout=10
    	Fetching changes from the remote Git repositories
    	 > "C:\git\cmd\git.exe" config remote.origin.url ssh://g...@builds.me.local/jk/testgitreponewbranch.git # timeout=10
    	Fetching upstream changes from ssh://g...@builds.me.local/jk/testgitreponewbranch.git
    	 > "C:\git\cmd\git.exe" --version # timeout=10
    	 > "C:\git\cmd\git.exe" fetch --tags --progress ssh://g...@builds.me.local/jk/testgitreponewbranch.git +refs/heads/*:refs/remotes/origin/*
    

    You can see the process never ending in taskmgr

However, running that last command manually (from a command prompt) does not result in hang, it exits immediately.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to