-
Bug
-
Resolution: Fixed
-
Major
-
None
00:00:47.915 hudson.plugins.git.GitException: Could not checkout null with start point 3a7a46bb869eff4f16b2974d8f3dba7f56ce27a8
We are trying to analyse this situation for quite some time now - but we honestly have no clue.
This situation is sometimes triggered because of force pushes to branches.
Sometimes it happens because of other branches being merged into master.
A workaround is to create a new branch and a new pull request. As soon as the job is executed on this new pull request (which holds the identical commits) the job executes just fine.
Soometimes is also helps to not touch the branch for days and simply retrigger the execution.
- is related to
-
JENKINS-10385 FATAL: Could not checkout null with start point after a reset --hard to remove a commit
-
- Open
-
-
JENKINS-22537 Seemingly random failures of GitHub plugin PR builder
-
- Open
-
Got same error on similar situations
10:57:11 Checking out Revision 4ffcf74053105974cf8a8663b78429ca08b42b59 (refs/remotes/origin/pr/1925/merge)
10:57:11 > git config core.sparsecheckout # timeout=10
10:57:11 > git checkout -f 4ffcf74053105974cf8a8663b78429ca08b42b59
10:57:11 FATAL: Could not checkout null with start point 4ffcf74053105974cf8a8663b78429ca08b42b59
10:57:11 hudson.plugins.git.GitException: Could not checkout null with start point 4ffcf74053105974cf8a8663b78429ca08b42b59
10:57:11 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$8.execute(CliGitAPIImpl.java:1855)
env: Cloudbees
GIT client plugin v1.16.1
GIT plugin v2.3.5
Github plugin v1.10
Github pull request builder v1.16-8