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

Bitbucket Server Pull Requests not being added to Multibranch Pipeline Status display

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Environment:
      Jenkins 2.86
      Bitbucket Server 4.11
      Bitbucket Branch Source Plugin 2.2.4

      All built in plugins were updated to latest versions 10/30, so should be latest/greatest for the pipeline functionality.
    • Similar Issues:

      Description

      My configuration settings are

      Discover branches -  All Branches

      Discover pull requests from origin - Both current and merged with target

      Filter by name for master and feature* branches

      My pipeline scan log appears to see it

      Looking up devts-bb/atlassian-elastic-stack for branches

      Checking branch feature/DEVTS-2678-configuration-git-repository from devts-bb/atlassian-elastic-stack
            ‘Jenkinsfile’ found
          Met criteria
      No changes detected: feature/DEVTS-2678-configuration-git-repository (still at 4d5d412c8fb56e9446d200287a83007cbc2e03d3)
      Checking branch master from devts-bb/atlassian-elastic-stack

            ‘Jenkinsfile’ found
          Met criteria
      No changes detected: master (still at 6d0688e7ee81e87b1142183c46e7a8d25fa0c91d)

        2 branches were processed
      Looking up devts-bb/atlassian-elastic-stack for pull requests
      Checking PR-3 from DEVTS-BB/atlassian-elastic-stack and branch feature/DEVTS-2678-configuration-git-repository

        1 pull requests were processed
      [Mon Oct 30 16:47:36 EDT 2017] Finished branch indexing. Indexing took 2.3 sec
      Finished: SUCCESS

      But the status page of the jobs shows 2 branches and 0 pull requests.

      Changing to other combinations of the discover settings does not make a difference.

      Let me know what other information would be useful. 

        Attachments

          Activity

          Hide
          netappbluedevil NetAppBlueDevil added a comment -

          This issue maybe should just be a documentation thing.  Based on other articles I found, adding "PR*" to the include filters with wildcards enabled the PR items to be found and listed.  I did not see such information in the setup documentation.

          Show
          netappbluedevil NetAppBlueDevil added a comment - This issue maybe should just be a documentation thing.  Based on other articles I found, adding "PR*" to the include filters with wildcards enabled the PR items to be found and listed.  I did not see such information in the setup documentation.
          Hide
          wotte William Otte added a comment -

          I am also seeing this same behavior.  I do have in my configuration 'PR*' in the included branches.

          I also observe that if I manually trigger a pipeline scan, the PR is discovered and a build scheduled.

          Show
          wotte William Otte added a comment - I am also seeing this same behavior.  I do have in my configuration 'PR*' in the included branches. I also observe that if I manually trigger a pipeline scan, the PR is discovered and a build scheduled.
          Hide
          donovanmuller Donovan Muller added a comment -

          William Otte I'm having exactly the same issue.

          Jenkins: 2.89.4
          cloudbees-bitbucket-branch-source: 2.2.14

          Bitbucket Server 5.10

          Show
          donovanmuller Donovan Muller added a comment - William Otte I'm having exactly the same issue. Jenkins: 2.89.4 cloudbees-bitbucket-branch-source: 2.2.14 Bitbucket Server 5.10

            People

            • Assignee:
              Unassigned
              Reporter:
              netappbluedevil NetAppBlueDevil
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated: