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

MultiBranch doesn't distinguish Branches and PRs

      jenkins.branch.Branch#getName uses head.getName
      That ends that branch name equals PR name makes branch api crazy.
      As example your github-branchsource-plugin https://ci.jenkins.io/job/Plugins/job/github-plugin/job/PR-182/ after branch appeared in Branches it disappeared in PullRequests and mixined build history.

      And guess revision https://ci.jenkins.io/job/Plugins/job/github-plugin/job/PR-182/5/

      Normally SCMCategories must be part of branch names or at all subfolders. And the easiest: enforce implementations to deal themselves with prefixes (that ideally are categories).

          [JENKINS-48226] MultiBranch doesn't distinguish Branches and PRs

          Kanstantsin Shautsou created issue -
          Kanstantsin Shautsou made changes -
          Description Original: {{jenkins.branch.Branch#getName}} uses {{head.getName}}
          That ends that branch name equals PR name makes branch api crazy.
          As example your github-branchsource-plugin https://ci.jenkins.io/job/Plugins/job/github-plugin/job/PR-182/ after branch appeared in Branches it disappeared in PullRequests and mixined build history.

          Normally SCMCategories must be part of branch names or at all subfolders.
          New: {{jenkins.branch.Branch#getName}} uses {{head.getName}}
          That ends that branch name equals PR name makes branch api crazy.
          As example your github-branchsource-plugin https://ci.jenkins.io/job/Plugins/job/github-plugin/job/PR-182/ after branch appeared in Branches it disappeared in PullRequests and mixined build history.

          Normally SCMCategories must be part of branch names or at all subfolders. And the easiest: enforce implementations to deal themselves with prefixes (that ideally are categories).
          Kanstantsin Shautsou made changes -
          Description Original: {{jenkins.branch.Branch#getName}} uses {{head.getName}}
          That ends that branch name equals PR name makes branch api crazy.
          As example your github-branchsource-plugin https://ci.jenkins.io/job/Plugins/job/github-plugin/job/PR-182/ after branch appeared in Branches it disappeared in PullRequests and mixined build history.

          Normally SCMCategories must be part of branch names or at all subfolders. And the easiest: enforce implementations to deal themselves with prefixes (that ideally are categories).
          New: {{jenkins.branch.Branch#getName}} uses {{head.getName}}
          That ends that branch name equals PR name makes branch api crazy.
          As example your github-branchsource-plugin https://ci.jenkins.io/job/Plugins/job/github-plugin/job/PR-182/ after branch appeared in Branches it disappeared in PullRequests and mixined build history.

          And guess revision https://ci.jenkins.io/job/Plugins/job/github-plugin/job/PR-182/5/ ;)

          Normally SCMCategories must be part of branch names or at all subfolders. And the easiest: enforce implementations to deal themselves with prefixes (that ideally are categories).
          Kanstantsin Shautsou made changes -
          Priority Original: Major [ 3 ] New: Critical [ 2 ]
          Kanstantsin Shautsou made changes -
          Priority Original: Critical [ 2 ] New: Blocker [ 1 ]
          Stephen Connolly made changes -
          Resolution New: Won't Fix [ 2 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Kanstantsin Shautsou made changes -
          Resolution Original: Won't Fix [ 2 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]
          Stephen Connolly made changes -
          Assignee Original: Stephen Connolly [ stephenconnolly ]

            Unassigned Unassigned
            integer Kanstantsin Shautsou
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: