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

Project checkout fails (ERROR: Could not determine exact tip revision of master)

XMLWordPrintable

      Our Jenkins started failing projects at the beginning of the year, our workaround was to limit the following plugin versions

      workflow-multibranch 2.9
workflow-aggregator 2.4

      It is working since this limitation, but we would like to use the latest plugin versions

       

      The Error was

      ERROR: Could not determine exact tip revision of master; falling back to nondeterministic checkout
[...]
Checking out Revision cec453d87cd2717fd4a392e2813b45d1c929b706 (origin/master)
[...]
Caught: hudson.AbortException: Could not determine exact tip revision of master
[...]
Caught: hudson.AbortException: Could not determine exact tip revision of master
[...]
ERROR: Could not determine exact tip revision of master

      -JENKINS-40862- Seems to be similar but was closed as "Incomplete"

          [JENKINS-46290] Project checkout fails (ERROR: Could not determine exact tip revision of master)

          Georg Steinmetz created issue -
          Georg Steinmetz made changes -
          Description Original: Our Jenkins started failing projects at the beginning of the year, our workaround was to limit the following plugin versions
          {code:java}
          workflow-multibranch 2.9
          workflow-aggregator 2.4{code}
          It is working since this limitation, but we would like to use the latest plugin versions

           

          The Error was
          {code:java}
          Started by timer
          ERROR: Could not determine exact tip revision of master; falling back to nondeterministic checkout{code}
          JENKINS-40862 Seems to be similar but was closed as "Incomplete"           		New: Our Jenkins started failing projects at the beginning of the year, our workaround was to limit the following plugin versions
          {code:java}
          workflow-multibranch 2.9
          workflow-aggregator 2.4{code}
          It is working since this limitation, but we would like to use the latest plugin versions

           

          The Error was
          {code:java}
          ERROR: Could not determine exact tip revision of master; falling back to nondeterministic checkout
          Caught: hudson.AbortException: Could not determine exact tip revision of master
          Caught: hudson.AbortException: Could not determine exact tip revision of master
          ERROR: Could not determine exact tip revision of master{code}
          -JENKINS-40862- Seems to be similar but was closed as "Incomplete"
          Georg Steinmetz made changes -
          Description Original: Our Jenkins started failing projects at the beginning of the year, our workaround was to limit the following plugin versions
          {code:java}
          workflow-multibranch 2.9
          workflow-aggregator 2.4{code}
          It is working since this limitation, but we would like to use the latest plugin versions

           

          The Error was
          {code:java}
          ERROR: Could not determine exact tip revision of master; falling back to nondeterministic checkout
          Caught: hudson.AbortException: Could not determine exact tip revision of master
          Caught: hudson.AbortException: Could not determine exact tip revision of master
          ERROR: Could not determine exact tip revision of master{code}
          -JENKINS-40862- Seems to be similar but was closed as "Incomplete"           		New: Our Jenkins started failing projects at the beginning of the year, our workaround was to limit the following plugin versions
          {code:java}
          workflow-multibranch 2.9
          workflow-aggregator 2.4{code}
          It is working since this limitation, but we would like to use the latest plugin versions

           

          The Error was
          {code:java}
          ERROR: Could not determine exact tip revision of master; falling back to nondeterministic checkout
          [...]
          Checking out Revision cec453d87cd2717fd4a392e2813b45d1c929b706 (origin/master)
          [...]
          Caught: hudson.AbortException: Could not determine exact tip revision of master
          [...]
          Caught: hudson.AbortException: Could not determine exact tip revision of master
          [...]
          ERROR: Could not determine exact tip revision of master{code}
          --JENKINS-40862-- Seems to be similar but was closed as "Incomplete"

          Stephen Connolly added a comment -

          Please reopen when you have more details. This is not sufficient to even understand where to start looking

          Stephen Connolly added a comment - Please reopen when you have more details. This is not sufficient to even understand where to start looking
          Stephen Connolly made changes -
          Resolution New: Incomplete [ 4 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          Chance Zibolski added a comment -

          I am also getting this in various cases. It's more common when an upstream job triggers the pipeline, but it happens on multibranch pipelines that don't get triggered by other jobs too.

          Chance Zibolski added a comment - I am also getting this in various cases. It's more common when an upstream job triggers the pipeline, but it happens on multibranch pipelines that don't get triggered by other jobs too.

          Will McKinley added a comment -

          I also ran into this issue this week.  I got the same error using a Jenkinsfile in a project that only has the Jenkinsfile in the develop branch currently.  My only recourse was to use command line Git in a shell directive to perform a checkout on the develop branch and then pull.

          Will McKinley added a comment - I also ran into this issue this week.  I got the same error using a Jenkinsfile in a project that only has the Jenkinsfile in the develop branch currently.  My only recourse was to use command line Git in a shell directive to perform a checkout on the develop branch and then pull.

          Will McKinley added a comment -

          I just noticed that the issue is in Resolved state.  How was it resolved?  Was there a code fix for it?

          Will McKinley added a comment - I just noticed that the issue is in Resolved state.  How was it resolved?  Was there a code fix for it?

          Sorin Sbarnea added a comment -

          I am reopening the issue because I found a way to replicate the issue: this happens when there was a forced push on the git server.

          The client needs to be able to detect this and to abort the build probably?

          Also, I suspect similar thing may happen if the workspace is not cleanup and there is a forced push on remote git. To prevent a permanent failure of all future jobs we need an option to perform a forced pull when such error occurs — as in a self-repairing local clone.

          Sorin Sbarnea added a comment - I am reopening the issue because I found a way to replicate the issue: this happens when there was a forced push on the git server. The client needs to be able to detect this and to abort the build probably? Also, I suspect similar thing may happen if the workspace is not cleanup and there is a forced push on remote git. To prevent a permanent failure of all future jobs we need an option to perform a forced pull when such error occurs — as in a self-repairing local clone.
          Sorin Sbarnea made changes -
          Resolution Original: Incomplete [ 4 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]

            Unassigned Unassigned
            gsteinmetz Georg Steinmetz
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: