[JIRA] [git-plugin] (JENKINS-33140) Git plugin doesn't use refspec on the first clone/fetch

[cuong.tran@gmail.com (JIRA)]

Cuong Tran created an issue

Jenkins / JENKINS-33140 Git plugin doesn't use refspec on the first clone/fetch Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 25/Feb/16 12:23 AM Environment: Jenkins ver. 1.649 Git plugin 2.4.2 Priority: Minor Reporter: Cuong Tran Our repositories have lots of references and we only need to build from a single branch from each job. For example, I have a job with refspec +refs/heads/master:refs/remotes/origin/master. On the first clone, it does the following: Cloning the remote Git repository Using shallow clone Avoid fetching tags Cloning repository https://github.com/foo.git > git init /tmp/jenkins/slave1/workspace/sample/smoke-test # timeout=10 Fetching upstream changes from https://github.com/foo.git > git --version # timeout=10 > git -c core.askpass=true fetch --no-tags --progress https://github.com/foo.git +refs/heads/:refs/remotes/origin/ --depth=1 # timeout=10 Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[cuong.tran@gmail.com (JIRA)]

Cuong Tran updated an issue

Jenkins / JENKINS-33140 Git plugin doesn't use refspec on the first clone/fetch

Change By: Cuong Tran

Our repositories have lots of references and we only need to build from a single branch from each job.  For example, I have a job with refspec +refs/heads/master:refs/remotes/origin/master.   On the first clone, it does the following: Cloning the remote Git repository Using shallow clone Avoid fetching tags Cloning repository https://github.com/foo.git  > git init /tmp/jenkins/slave1/workspace/sample/smoke-test # timeout=10 Fetching upstream changes from https://github.com/foo.git  > git --version # timeout=10

> git -c core.askpass=true fetch --no-tags --progress https://github.com/foo.git +refs/heads/* * :refs/remotes/origin/* *  --depth=1 # timeout=10

Add Comment

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

Mark Waite assigned an issue to Unassigned

Jenkins / JENKINS-33140 Git plugin doesn't use refspec on the first clone/fetch

Change By: Mark Waite Assignee: Mark Waite

Add Comment

[timocov@gmail.com (JIRA)]

Eugene Timokhov commented on JENKINS-33140

Re: Git plugin doesn't use refspec on the first clone/fetch Duplicate https://issues.jenkins-ci.org/browse/JENKINS-31393

Add Comment

[timocov@gmail.com (JIRA)]

Eugene Timokhov closed an issue as Duplicate

Jenkins / JENKINS-33140

Git plugin doesn't use refspec on the first clone/fetch

Change By: Eugene Timokhov Status: Open Closed Resolution: Duplicate

Add Comment

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

Mark Waite commented on JENKINS-33140

Re: Git plugin doesn't use refspec on the first clone/fetch Fixed in git plugin 2.5.1

Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[javibm6@gmail.com (JIRA)]

Javier Agüera reopened an issue

Hey, I'm getting the same exactly bug with version 3.0.5 and Jenkins: 2.32.2. The steps to reproduce the issue are the same. Is it possible to have a regression here? Thanks.

Jenkins / JENKINS-33140

Git plugin doesn't use refspec on the first clone/fetch

Change By: Javier Agüera Resolution: Duplicate Status: Closed Reopened

Add Comment

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

Mark Waite resolved as Fixed

What you're seeing is not a regression. It is an intentional choice that the default behavior had to remain compatible with the behavior which caused this bug report and JENKINS-31393. One or more use cases depended on the bug that the default initial fetch retrieved all refspecs, even if a refspec was provided. I was unable to find any way to make those use cases work other than to leave the default behavior as it was before this bug was fixed. Users who need to honor the refspec on initial clone will need to modify their job definition to add that to the job definition. The "Advanced clone behaviours" available in the "Add" button of the git plugin configuration section now includes a check box "Honor refspec on initial clone". You need to check that box for all jobs where you want to honor refspec on initial clone.

Jenkins / JENKINS-33140 Git plugin doesn't use refspec on the first clone/fetch

Change By: Mark Waite Status: Reopened Resolved Resolution: Fixed

Add Comment

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

Mark Waite closed an issue as Fixed

Jenkins / JENKINS-33140 Git plugin doesn't use refspec on the first clone/fetch

Change By: Mark Waite Status: Resolved Closed

Add Comment

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