Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-11953

Pull Request refs are not recreated on re-open.

XMLWordPrintable

      Issue Summary

      When declining a PR, the refs/pull-request/<PR ID> is not recreated when the PR is reopened

      Steps to Reproduce

      1. Create a pull request
      2. Navigate to <Bitbucket shared>/data/repositories/<repo slug>/refs/pull-requests
      3. Note the ID of your PR exists
      4. Decline the PR and note that the PR ID is gone (expected)
      5. Reopen the PR

      Expected Results

      The directory for the PR is recreated

      Actual Results

      The directory for the PR is not recreated

      Workaround

      Pushing any change to the master or source branch before OR after the PR is reopened will cause the directory to be created when the PR is open.

          Form Name

            [BSERV-11953] Pull Request refs are not recreated on re-open.

            Ricardo Deitoz Posser added a comment -

            Thank you for the answer Bryan

            Ricardo Deitoz Posser added a comment - Thank you for the answer Bryan

            Bryan Turner (Inactive) added a comment -

            ricardo.posser,

            Bitbucket Server 6.8.0 includes the fix (as do all later versions, currenly 6.8.1 and 6.9.0); I just forgot to update this issue. Point releases for 6.4-6.7 are still pending, but likely to happen in the next 2-4 weeks (it's the holidays, so timetables are a bit loose right now). They haven't been cut previously because we've been accumulating some other fixes.

            Best regards,
            Bryan Turner
            Atlassian Bitbucket

            Bryan Turner (Inactive) added a comment - ricardo.posser , Bitbucket Server 6.8.0 includes the fix (as do all later versions, currenly 6.8.1 and 6.9.0); I just forgot to update this issue. Point releases for 6.4-6.7 are still pending, but likely to happen in the next 2-4 weeks (it's the holidays, so timetables are a bit loose right now). They haven't been cut previously because we've been accumulating some other fixes. Best regards, Bryan Turner Atlassian Bitbucket

            Ricardo Deitoz Posser added a comment -

            I see this is waiting for release since october.
            Do you have any idea when it will be released?

            Ricardo Deitoz Posser added a comment - I see this is waiting for release since october. Do you have any idea when it will be released?

            Caio Cezar Zapater de Souza added a comment -

            This my error on Jenkins

            Caio Cezar Zapater de Souza added a comment - This my error on Jenkins

            Caio Cezar Zapater de Souza added a comment -

            I have an automated pipeline running on Jenkins that rely on this feature, and I believe the entire community that uses Jenkins with Bitbucket and PR are affected, because this is the default behaviour for [Multibranch Pipeline|https://jenkins.io/doc/tutorials/build-a-multibranch-pipeline-project/]

            After a PR is declined, Jenkins cannot clone de repo, the ref is no logger available.

            Caio Cezar Zapater de Souza added a comment - I have an automated pipeline running on Jenkins that rely on this feature, and I believe the entire community that uses Jenkins with Bitbucket and PR are affected, because this is the default behaviour for [Multibranch Pipeline| https://jenkins.io/doc/tutorials/build-a-multibranch-pipeline-project/ ] After a PR is declined, Jenkins cannot clone de repo, the ref is no logger available.

              bturner Bryan Turner (Inactive)
              alevinson Aaron
              Affected customers:
              29 This affects my team
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: