[JIRA] [git-plugin] (JENKINS-34218) Shallow clone broken after JENKINS-24728
Title: Message Title Joshua Spence commented on JENKINS-34218 Re: Shallow clone broken after JENKINS-24728 Since filing this ticket we have simply stopped using shallow clone. As such, I can't easily reproduce this problem at the moment. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-34218) Shallow clone broken after JENKINS-24728
Title: Message Title Mark Waite commented on JENKINS-34218 Re: Shallow clone broken after JENKINS-24728 The next time that job fails, can you interactively perform a clone with --depth=1 and check if the SHA1 the job is trying to checkout is included in the shallow clone ofthe repository? I suspect it is not included in the shallow clone, almost as though the initial shallow clone needs to specify that exact SHA1 as the thing it is cloning. For example, if the initial clone is depth=1, and the sha1 being built is not the tip of that clone, then I would expect that sha1 to not be included in the repository (since the depth was 1). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-34218) Shallow clone broken after JENKINS-24728
Title: Message Title Joshua Spence commented on JENKINS-34218 Re: Shallow clone broken after JENKINS-24728 > What version of command line git are you running on the computer which shows the problem? 2.7.4 > If you run the same job again, does it then succeed? Yes, subsequent runs of the job seem to succeed. > Have you configured any other "Additional Behaviours" in the failing job? Yes, we also have "Check out to a specific local branch" with the branch name set to "" (empty string), "prune stale remote-tracking branches" and "clean after checkout". > Does the same problem happen on every job which uses a shallow clone? Actually, we only have a single job which uses shallow clone so I am unable to verify this. > Was the source repository involved in any form of cleanup or deletion of commits or content? JENKINS-10571 seems to suggest that the same message may happen when a branch is deleted from the source repository. No, we never remove commits from this repository. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-34218) Shallow clone broken after JENKINS-24728
Title: Message Title Mark Waite edited a comment on JENKINS-34218 Re: Shallow clone broken after JENKINS-24728 What version of command line git are you running on the computer which shows the problem?If you run the same job again, does it then succeed?Have you configured any other "Additional Behaviours" in the failing job?Does the same problem happen on every job which uses a shallow clone?Can you provide a series of steps which will duplicate the problem?Does the problem resolve itself if you use the earlier git plugin version (for example 2.4.2, don't use 2.4.3, it contains a job definition data loss bug that you don't want in your Jenkins)?Was the source repository involved in any form of cleanup or deletion of commits or content? JENKINS-10571 seems to suggest that the same message may happen when a branch is deleted from the source repository. Where is 1f2bf20dfc5a408d56181c9db99ac994545f44c3 in the history of that repository? For example, is it the tip of the branch that is to be built, or is it somewhere deeper than 1 commit into the history of the repository?If you set a depth greater than 1, does that resolve the issue?If you don't perform a shallow checkout, does that resolve the issue? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-34218) Shallow clone broken after JENKINS-24728
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-34218 Shallow clone broken after JENKINS-24728 Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-34218) Shallow clone broken after JENKINS-24728
Title: Message Title Mark Waite edited a comment on JENKINS-34218 Re: Shallow clone broken after JENKINS-24728 What version of command line git are you running on the computer which shows the problem?If you run the same job again, does it then succeed?Have you configured any other "Additional Behaviours" in the failing job?Does the same problem happen on every job which uses a shallow clone?Can you provide a series of steps which will duplicate the problem?Does the problem resolve itself if you use the earlier git plugin version (for example 2.4.2, don't use 2.4.3, it contains a job definition data loss bug that you don't want in your Jenkins)? Was the source repository involved in any form of cleanup or deletion of commits or content? JENKINS-10571 seems to suggest that the same message may happen when a branch is deleted from the source repository. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-34218) Shallow clone broken after JENKINS-24728
Title: Message Title Mark Waite edited a comment on JENKINS-34218 Re: Shallow clone broken after JENKINS-24728 What version of command line git are you running on the computer which shows the problem?If you run the same job again, does it then succeed?Have you configured any other "Additional Behaviours" in the failing job?Does the same problem happen on every job which uses a shallow clone?Can you provide a series of steps which will duplicate the problem? Does the problem resolve itself if you use the earlier git plugin version (for example 2.4.2, don't use 2.4.3, it contains a job definition data loss bug that you don't want in your Jenkins)? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-34218) Shallow clone broken after JENKINS-24728
Title: Message Title Mark Waite commented on JENKINS-34218 Re: Shallow clone broken after JENKINS-24728 What version of command line git are you running on the computer which shows the problem? If you run the same job again, does it then succeed? Have you configured any other "Additional Behaviours" in the failing job? Does the same problem happen on every job which uses a shallow clone? Can you provide a series of steps which will duplicate the problem? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-34218) Shallow clone broken after JENKINS-24728
Title: Message Title Joshua Spence created an issue Jenkins / JENKINS-34218 Shallow clone broken after JENKINS-24728 Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2016/Apr/14 1:15 AM Environment: git-plugin 2.4.4 Priority: Critical Reporter: Joshua Spence JENKINS-24728 broke our use of shallow clone. Basically, we are getting the following error: ``` > git config remote.origin.url git@REDACTED # timeout=10 Pruning obsolete local branches Fetching upstream changes from git@REDACTED > git --version # timeout=10 using GIT_SSH to set credentials > git -c core.askpass=true fetch --tags --progress git@REDACTED +refs/heads/:refs/remotes/origin/ --prune --depth=1 Checking out Revision 1f2bf20dfc5a408d56181c9db99ac994545f44c3 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 1f2bf20dfc5a408d56181c9db99ac994545f44c3 # timeout=10 FATAL: Could not checkout master with start point 1f2bf20dfc5a408d56181c9db99ac994545f44c3 hudson.plugins.git.GitException: Could not checkout master with start point 1f2bf20dfc5a408d56181c9db99ac994545f44c3 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:1990) at org.jenkinsci.plugins.gitclient.RemoteGitIm
