Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-26748

Git plugin sometimes reports Could not checkout null with start point <SHA1>

    Details

    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            Hide
            vietsoft vietsoft added a comment -

            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

            Show
            vietsoft vietsoft added a comment - 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
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Nicolas De Loof
            Path:
            src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java
            http://jenkins-ci.org/commit/git-client-plugin/0d477d77553b379b84cdb852771e94c5e9dbafd6
            Log:
            JENKINS-26748 avoid null in error log when no branch specified

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Nicolas De Loof Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/0d477d77553b379b84cdb852771e94c5e9dbafd6 Log: JENKINS-26748 avoid null in error log when no branch specified
            Hide
            integer Kanstantsin Shautsou added a comment -

            github-api-plugin is just a wrapper for existed library, please assign right component.

            Show
            integer Kanstantsin Shautsou added a comment - github-api-plugin is just a wrapper for existed library, please assign right component.
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Mark Waite
            Path:
            pom.xml
            http://jenkins-ci.org/commit/git-client-plugin/3bd20ddf480daf6794ba2a8de54007a8894c65a1
            Log:
            Base 1.17.1 off 1.16.1: allow more study of git 2.3.6-SNAPSHOT issues

            The release of git client plugin 1.17.0 delivered a fix for
            [ISO date parsing](https://issues.jenkins-ci.org/browse/JENKINS-27097).
            Unfortunately, that fix exposes a long-standing bug in git plugin versions
            2.3.5 and earlier. The bug is fixed in git plugin 2.3.6-SNAPSHOT.
            However, tests of git plugin 2.3.6-SNAPSHOT show that it is not yet
            ready for production use.

            Rather than rush to deliver git plugin 2.3.6, this change will restore the
            git client plugin to the code base which was delivered with git client
            plugin 1.16.1. That will hide the ISO date parsing bug that is in git
            plugin 2.3.5 and earlier and allow more time to prepare 2.3.6 for release.

            The 1.17.0 changes are not included in this build, including:

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Mark Waite Path: pom.xml http://jenkins-ci.org/commit/git-client-plugin/3bd20ddf480daf6794ba2a8de54007a8894c65a1 Log: Base 1.17.1 off 1.16.1: allow more study of git 2.3.6-SNAPSHOT issues The release of git client plugin 1.17.0 delivered a fix for [ISO date parsing] ( https://issues.jenkins-ci.org/browse/JENKINS-27097 ). Unfortunately, that fix exposes a long-standing bug in git plugin versions 2.3.5 and earlier. The bug is fixed in git plugin 2.3.6-SNAPSHOT. However, tests of git plugin 2.3.6-SNAPSHOT show that it is not yet ready for production use. Rather than rush to deliver git plugin 2.3.6, this change will restore the git client plugin to the code base which was delivered with git client plugin 1.16.1. That will hide the ISO date parsing bug that is in git plugin 2.3.5 and earlier and allow more time to prepare 2.3.6 for release. The 1.17.0 changes are not included in this build, including: Update minimum Jenkins version from 1.509 to 1.532.2 Update JGit to 3.7.0 [Allow prune with JGit JENKINS-26197] ( https://issues.jenkins-ci.org/browse/JENKINS-26197 ) [Use ISO-8601 date format in changelog JENKINS-27097] ( https://issues.jenkins-ci.org/browse/JENKINS-27097 ) [Improve checkout failure message JENKINS-26748] ( https://issues.jenkins-ci.org/browse/JENKINS-26748 ) Guard against null pointer exception in several API calls Update other dependencies
            Hide
            markewaite Mark Waite added a comment -

            The git plugin and git client plugin are being tested in hopes of releasing new versions before the end of June. The new versions include a fix for this message about "could not checkout null".

            If you're willing to assist with the testing, please download and install a pre-release build of the git client plugin and the git plugin. Problems detected in the pre-release should be e-mailed to Mark Waite and Nicolas De Loof.

            I wrote some test ideas if you would like suggestions of areas that need testing. The git plugin supports many different use cases and its automated tests only evaluate a very few of those use cases.

            Show
            markewaite Mark Waite added a comment - The git plugin and git client plugin are being tested in hopes of releasing new versions before the end of June. The new versions include a fix for this message about "could not checkout null". If you're willing to assist with the testing, please download and install a pre-release build of the git client plugin and the git plugin . Problems detected in the pre-release should be e-mailed to Mark Waite and Nicolas De Loof . I wrote some test ideas if you would like suggestions of areas that need testing. The git plugin supports many different use cases and its automated tests only evaluate a very few of those use cases.
            Hide
            nneul Nathan Neulinger added a comment -

            We're seeing this problem (likely due to some dev teams frequently force pushing). Trying the binaries you listed in comment above.

            Show
            nneul Nathan Neulinger added a comment - We're seeing this problem (likely due to some dev teams frequently force pushing). Trying the binaries you listed in comment above.
            Hide
            markewaite Mark Waite added a comment -

            Message has been improved, and general issue may be resolved by git client plugin 1.18.0 released 18 July 2015

            Show
            markewaite Mark Waite added a comment - Message has been improved, and general issue may be resolved by git client plugin 1.18.0 released 18 July 2015

              People

              • Assignee:
                ndeloof Nicolas De Loof
                Reporter:
                deepdiver Thomas Müller
              • Votes:
                4 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: