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

BO PR view does not honor "Discover pull request" settings

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • blueocean-plugin
    • None
    • Jenkins core 2.155
      BO 1.9

      If you set "Discover pull requests from forks" to "Both the current pull request revision and the pull request merged with the current target branch revision" then the build from PR-merge and PR-head would be mixed on the BO PR view.

          [JENKINS-55201] BO PR view does not honor "Discover pull request" settings

          Fred Vogt added a comment -

          This is still a problem as of 2.241 (2020-06-16).

          I like the option of building both the HEAD/MERGE simultaneously.

          Its a usability issue if the 'PR-N-head', 'PR-N-merge' can't be distinguished in "Pull Requests" tab.

          Fred Vogt added a comment - This is still a problem as of 2.241 (2020-06-16). I like the option of building both the HEAD/MERGE simultaneously. Its a usability issue if the 'PR-N-head', 'PR-N-merge' can't be distinguished in "Pull Requests" tab.

          Fred Vogt added a comment - - edited

          Added some extra screenshots.

          The "Activity" tab of the Pipelines activity view has the "Branch" column.

          The "Pull Requests" tab could either add the "-head / -merge" suffix when using:

          Fred Vogt added a comment - - edited Added some extra screenshots. The "Activity" tab of the Pipelines activity view has the "Branch" column. The "Pull Requests" tab could either add the "-head / -merge" suffix when using: jenkinsci/github-branch-source-plugin/org/jenkinsci/plugins/github_branch_source/OriginPullRequestDiscoveryTrait.java - BOTH

            Unassigned Unassigned
            ifernandezcalvo Ivan Fernandez Calvo
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: