• Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • None
    • Jenkins 2.258
      Stash Pull Requests Builder 1.17

      Getting the following error when trying to build pull requests after upgrading to Bitbucket 7.6.0:

       
      {{> C:\Program Files\Git\bin\git.exe fetch --tags --force --progress – REDACTED_URL +refs/pull-requests/:refs/remotes/origin/pr/ # timeout=10}}
      {{ > C:\Program Files\Git\bin\git.exe rev-parse "refs/remotes/origin/pr/140/from^{commit}" # timeout=10}}
      {{ > C:\Program Files\Git\bin\git.exe rev-parse "origin/pr/140/from^{commit}" # timeout=10}}
      {{ ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.}}

      I've tried pulling the ref manually, and while some of the older refs are there, pull requests made after the upgrade are not. Is the ref no longer available? I understand that may be "Bitbucket's fault", but if the mechanism this plugin uses is gone, then isn't the plugin broken?

          [JENKINS-63802] Couldn't find any revision to build

          This plugin only supplies the metadata in form of environment variables.
          Please consult Stash and/or the Git plugin documentation on how to do the checkout

          Jakub Bochenski added a comment - This plugin only supplies the metadata in form of environment variables. Please consult Stash and/or the Git plugin documentation on how to do the checkout

          Todd Boyd added a comment -

          You should update your documentation on Git, then, as the suggested way to configure the PR builder is inaccurate and broken.

          Todd Boyd added a comment - You should update your documentation on Git, then, as the suggested way to configure the PR builder is inaccurate and broken.

            jbochenski Jakub Bochenski
            tmboyd1 Todd Boyd
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: