[JIRA] (JENKINS-61127) More freely defined advanced clone behaviours

[tor.christian.solevagseide@meritglobe.com (JIRA)]

Tor Christian Solevågseide created an issue

Jenkins / JENKINS-61127 More freely defined advanced clone behaviours Issue Type: Improvement Assignee: Mark Waite Components: git-plugin Created: 2020-02-18 13:38 Priority: Major Reporter: Tor Christian Solevågseide There is a need for a "More advanced clone behaviors" The current "Advanced clone behaviours" takes us just part of the way when needing to configure the clone operation. There are a lot of options on git clone that is not possible to set. Ref https://git-scm.com/docs/git-clone Example: We currently have the need to do a shallow clone, but need to include all branches. Meaning that we want to add the --no-single-branch option. We cannot see any other way of achieving this right now. I assume this request will solve JENKINS-61109 and similar issues as well. Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite commented on JENKINS-61127

Re: More freely defined advanced clone behaviours A shallow clone with all branches is the default when shallow clone is enabled. The default refspec pulls all branches. For historical reasons, the Jenkins git plugin uses a combination of git init and git fetch to populate its workspaces. I don't expect that to change in the future because it would be very likely to break many, many Jenkins users.

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite assigned an issue to Unassigned

Jenkins / JENKINS-61127

More freely defined advanced clone behaviours

Change By: Mark Waite Assignee: Mark Waite

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite edited a comment on JENKINS-61127

Re: More freely defined advanced clone behaviours

A shallow clone with all branches is the default when shallow clone is enabled.  The default refspec pulls all branches.

For historical reasons, the Jenkins git plugin uses a combination of {{git init}} and {{git fetch}} to populate its workspaces.  I don't expect that to change in the future because it would be very likely to break many, many Jenkins users.   If the git plugin were to use {{git clone}} directly, it would need to be through a completely new code path so that the existing behaviors would be retained.

Add Comment