Mark Waite resolved Improvement JENKINS-8593 as Fixed

I've confirmed that this is no longer an issue with git-client-plugin 1.6.2 and git-plugin 2.0.1 and later. I verified it with both the command line implementation and the JGit implementation.

Steps I took:

  • Create an empty bare repository on my git server (git protocol)
  • Define a job which clones that bare repository
  • Run that job and confirm the job fails (no revision to checkout)
  • Push a change to that bare repository from a clone made elsewhere
  • Run the job again and confirm that the job succeeds
Change By: Mark Waite (25/Feb/14 12:49 AM)
Status: Open Resolved
Resolution: Fixed
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/groups/opt_out.

Reply via email to