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

Upstream project trigger tip revision error

XMLWordPrintable

      Hi,

      I have a project which triggers a build in another project (pipeline / Jenkinsfile).

      {
....
    build job: "../projectName/master";
}

      However, the downstream project gives errors out with the following error: 

      originally caused by:
 Branch indexing
ERROR: Could not determine exact tip revision of master; falling back to nondeterministic checkout
Wiping out workspace first.
....
....
[Pipeline] End of Pipeline
ERROR: Could not determine exact tip revision of master
Finished: FAILURE

      Can this be solved somehow?

          [JENKINS-40862] Upstream project trigger tip revision error

          Rolph Haspers created issue -
          Rolph Haspers made changes -
          Labels Original: pipeline tip New: failure pipeline tip
          Rolph Haspers made changes -
          Priority Original: Major [ 3 ] New: Blocker [ 1 ]

          Ryan Currah added a comment -

          We are getting the same issue on Jenkins 2.40 and it seems to be related to upgrading to scm 2.0.

          We have tried using "build job" and "triggerRemoteJob" functions and both result in the same error.

          build job:

          build job: 'eis-factory-images/efr/helloworld/master', parameters: [string(name: 'GIT_BRANCH', value: 'master')]

          triggerRemoteJob:

          triggerRemoteJob mode: [$class: 'TrackProgressAwaitResult', scheduledTimeout: [timeoutStr: ''], startedTimeout: [timeoutStr: ''], timeout: [timeoutStr: '1d'], whenFailure: [$class: 'StopAsFailure'], whenScheduledTimeout: [$class: 'ContinueAsIs'], whenStartedTimeout: [$class: 'ContinueAsIs'], whenTimeout: [$class: 'ContinueAsFailure'], whenUnstable: [$class: 'ContinueAsUnstable']], remotePathMissing: [$class: 'ContinueAsIs'], remotePathUrl: "jenkins://323n1233j123123123/eis-factory-images/efr/helloworld/master

          Results in....

          Started by upstream project "eis-factory-images/pipeline_test" build number 4
originally caused by:
 Started by user Ryan Currah (Ryan.Currah)
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
[Pipeline] error
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // load
[Pipeline] }
[Pipeline] // dir
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
[Bitbucket] Notifying commit build result
[Bitbucket] Build result notified
ERROR: Could not determine exact tip revision of master
Finished: FAILURE

          Ryan Currah added a comment - We are getting the same issue on Jenkins 2.40 and it seems to be related to upgrading to scm 2.0. We have tried using "build job" and "triggerRemoteJob" functions and both result in the same error. build job: build job: 'eis-factory-images/efr/helloworld/master' , parameters: [string(name: 'GIT_BRANCH' , value: 'master' )] triggerRemoteJob: triggerRemoteJob mode: [$class: 'TrackProgressAwaitResult' , scheduledTimeout: [timeoutStr: ''], startedTimeout: [timeoutStr: ' '], timeout: [timeoutStr: ' 1d '], whenFailure: [$class: ' StopAsFailure '], whenScheduledTimeout: [$class: ' ContinueAsIs '], whenStartedTimeout: [$class: ' ContinueAsIs '], whenTimeout: [$class: ' ContinueAsFailure '], whenUnstable: [$class: ' ContinueAsUnstable ']], remotePathMissing: [$class: ' ContinueAsIs'], remotePathUrl: "jenkins: //323n1233j123123123/eis-factory-images/efr/helloworld/master Results in.... Started by upstream project "eis-factory-images/pipeline_test" build number 4 originally caused by: Started by user Ryan Currah (Ryan.Currah) 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 [Pipeline] error [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // load [Pipeline] } [Pipeline] // dir [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline [Bitbucket] Notifying commit build result [Bitbucket] Build result notified ERROR: Could not determine exact tip revision of master Finished: FAILURE
          Rolph Haspers made changes -
          Component/s New: workflow-multibranch-plugin [ 21465 ]

          Jesse Glick added a comment -

          Perhaps the master branch is dead for whatever reason? Cannot evaluate without a way to reproduce from scratch.

          ryancurrah you seem to be a CloudBees customer so you should open a support request.

          Jesse Glick added a comment - Perhaps the master branch is dead for whatever reason? Cannot evaluate without a way to reproduce from scratch. ryancurrah you seem to be a CloudBees customer so you should open a support request.
          Jesse Glick made changes -
          Resolution New: Incomplete [ 4 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          Chance Zibolski added a comment -

          I'm also hitting this periodcally, even after a successful build, sometimes the next one triggered fails. I'm using SCM API version 2.2.0 and Jenkins 2.60.2

          Chance Zibolski added a comment - I'm also hitting this periodcally, even after a successful build, sometimes the next one triggered fails. I'm using SCM API version 2.2.0 and Jenkins 2.60.2

          Antoine Le Maire added a comment - - edited

          I am also hitting this issue on a multi-branch pipeline job after successfull builds. "Scan Multibranch Pipeline Now" works around the issue but it is not a viable workaround as I have to re-scan all my multibranch pipelines manually every second day. I am using Jenkins 2.78 and SCM API 2.2.1.

          The issue is marked as closed, has it been fixed ?

          Antoine Le Maire added a comment - - edited I am also hitting this issue on a multi-branch pipeline job after successfull builds. "Scan Multibranch Pipeline Now" works around the issue but it is not a viable workaround as I have to re-scan all my multibranch pipelines manually every second day. I am using Jenkins 2.78 and SCM API 2.2.1. The issue is marked as closed, has it been fixed ?
          Chance Zibolski made changes -
          Status Original: Resolved [ 5 ] New: In Review [ 10005 ]

            daspilker Daniel Spilker
            rolphh Rolph Haspers
            Votes:
            11 Vote for this issue
            Watchers:
            22 Start watching this issue

              Created:
              Updated:
              Resolved: