[JIRA] (JENKINS-61469) Checkout fails with ERROR: Could not determine exact tip revision of <branch>

[felipecassiors@gmail.com (JIRA)]

Felipe Santos created an issue

Jenkins / JENKINS-61469 Checkout fails with ERROR: Could not determine exact tip revision of <branch> Issue Type: Bug Assignee: Luca Domenico Milanesio Attachments: image-2020-03-13-10-08-19-925.png Components: gerrit-code-review-plugin Created: 2020-03-13 13:08 Environment: Jenkins v2.225 Gerrit Code Review plugin v0.4.1 Gerrit v2.14 Priority: Major Reporter: Felipe Santos Hi, I'm experiencing this issue in one of my projects, using this plugin.   The issue is the same as the others linked (and closed) but happens using the Gerrit Code Review plugin. Seems like a fix was applied for BlueOcean, Github, Jervis, but I suppose this must also be fixed here.  Every time I push a new change for review, the first build of that patchset works. But if you hit Build now on that change, the build fails.  The error is: ```log ERROR: Could not determine exact tip revision of 01/7002801/3 ``` Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[mstory@arista.com (JIRA)]

Matt Story commented on JENKINS-61469

Re: Checkout fails with ERROR: Could not determine exact tip revision of <branch> I run into this issue when triggering a multibranch plugin job from another multibranch plugin job with 'build job: ...'.  When I build the job manually it works fine. Jenkins v2.202 GCR plugin version unknown since I don't have 'Manage Jenkins' privs. Gerrit v3.0.2

Add Comment

[felipecassiors@gmail.com (JIRA)]

Felipe Santos updated an issue

Jenkins / JENKINS-61469

Checkout fails with ERROR: Could not determine exact tip revision of <branch>

Change By: Felipe Santos

Hi, I'm experiencing this issue in one of my projects, using this plugin.   The issue is the same as the others linked (and closed) but happens using the Gerrit Code Review plugin. Seems like a fix was applied for BlueOcean, Github, Jervis, but I suppose this must also be fixed here.  Every time I push a new change for review, the first build of that patchset works. But if you hit Build now on that change, the build fails.  The error is:

```log {code:java} ERROR: Could not determine exact tip revision of 01/7002801/3 {code} ``` A picture of the pipeline: !image-2020-03-13-10-08-19-925.png!

Add Comment

[felipecassiors@gmail.com (JIRA)]

Felipe Santos commented on JENKINS-61469

Re: Checkout fails with ERROR: Could not determine exact tip revision of <branch> There are two workarounds 1. Use Jenkins Job Builder to create the Multibranch Pipeline on Jenkins      How-to: https://jenkins-job-builder.readthedocs.io/en/latest/project_workflow_multibranch.html#project_multibranch.gerrit_scm 2. Use Job DSL to create the Multibranch Pipeline on Jenkins

Add Comment

[felipecassiors@gmail.com (JIRA)]

Felipe Santos updated an issue

Jenkins / JENKINS-61469

Checkout fails with ERROR: Could not determine exact tip revision of <branch>

Change By: Felipe Santos ## h2. Short explanation : Creating Multibranch Pipelines using Gerrit as Branch Source through the UI causes the error to occur. The error is that for every new Change Request, the first build (and automatic) occurs with no problem, but if you hit Build Now to build a second, it fails with the error stated.  This error doesn't happen if you use Jenkins Job Builder or Job DSL to create the Multibranch pipeline, only when created by the UI. ## h2. Long explanation :

The issue is the same as the others linked (and closed) but happens using the Gerrit Code Review plugin. Seems like a fix was applied for BlueOcean, Github, Jervis, but I suppose this must also be fixed here.  Every time I push a new change for review, the first build of that patchset works. But if you hit Build now on that change, the build fails.  The error is:

{code:java} ERROR: Could not determine exact tip revision of 01/7002801/3{code} A picture of the pipeline: !image-2020-03-13-10-08-19-925.png!

Add Comment

[felipecassiors@gmail.com (JIRA)]

Felipe Santos updated an issue

Jenkins / JENKINS-61469 Checkout fails with ERROR: Could not determine exact tip revision of <branch> Change By: Felipe Santos

Hi ## Short explanation: Creating Multibranch Pipelines using Gerrit as Branch Source through the UI causes the error to occur. The error is that for every new Change Request , the first build (and automatic) occurs with no problem, but if you hit Build Now to build a second, it fails with the error stated.  I This error doesn ' m experiencing this issue in one of my projects t happen if you use Jenkins Job Builder or Job DSL to create the Multibranch pipeline , using this plugin only when created by the UI .   ## Long explanation:

The issue is the same as the others linked (and closed) but happens using the Gerrit Code Review plugin. Seems like a fix was applied for BlueOcean, Github, Jervis, but I suppose this must also be fixed here.  Every time I push a new change for review, the first build of that patchset works. But if you hit Build now on that change, the build fails.  The error is: {code:java} ERROR: Could not determine exact tip revision of 01/7002801/3{code} A picture of the pipeline: !image-2020-03-13-10-08-19-925.png!

Add Comment

[felipecassiors@gmail.com (JIRA)]

Felipe Santos updated an issue

Jenkins / JENKINS-61469 Checkout fails with ERROR: Could not determine exact tip revision of <branch>

Change By: Felipe Santos

Environment: Jenkins v2.225 Gerrit Code Review plugin v0.4.1 Gerrit v2.14

Add Comment