[JIRA] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Title: Message Title Nicolas De Loof assigned an issue to Unassigned Jenkins / JENKINS-14572 Git plug-in fetches all tags even when refspec is provided Change By: Nicolas De Loof Assignee: Nicolas De Loof Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.
[JIRA] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Title: Message Title Alexey Ostrovsky reopened an issue Git plugin does not respect 'Honor refspec on initial clone' in case if refs pointed to tags. All tags are fetched anyway. Jenkins / JENKINS-14572 Git plug-in fetches all tags even when refspec is provided Change By: Alexey Ostrovsky Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Title: Message Title Alexey Ostrovsky commented on JENKINS-14572 Re: Git plug-in fetches all tags even when refspec is provided That issue is still there. It does work whith branches but not with tags. With branches I had to configure "Do not fetch tags" to stop fetching all tags. But when I do the same for '+refs/tags/ci-uat' it does not find any release for the build as no any tags fetched. If I remove ""Do not fetch tags"" it fetches all tags. Refspec: +refs/tags/ci-uat Honor refspec on initial clone: enabled Jenkins: 2.27 Git plugin: 3.0.0 Git client plugin: 2.0.0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Douglas Beatty commented on JENKINS-14572 Git plug-in fetches all tags even when refspec is provided Copied the following comment from JENKINS-6124 as it is relevant here as well For a standard source code repository, this is not significant performance wise and we have not noticed this issue on our source code repositories. However, in general, it is not good that it is fetching references and therefore objects that are not required by the build. It is just inefficient. However, as stated, for source code repositories it is not significant enough that we have noticed. I have created a new issue that targets the scenario for our specific issue JENKINS-14572. Where we have noticed it is in the Git repositories we are using to deploy our web applications which are large repositories of binary files. We create each deployment image as an orphan commit, tag it, and push the tag not the branch back to our Git server. This way we can delete the tags after a holding period causing those commits to be unreferenced and eligible for garbage collection. We have the Jenkins plug-in configured to pull down an 'empty' branch by specifying a refspec. When all of the tags are fetched, then a large number of unneeded objects are pulled down from the repository greatly increasing the size of the repositories on the Jenkins slaves. Having said all of that, if you want to build a specific tag, why not specify it in the refspec? The refspec can use build parameters also. Why fetch all tags when you only need one? 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
