• Icon: Improvement Improvement
    • Resolution: Duplicate
    • Icon: Minor Minor
    • blueocean-plugin
    • None

      The current view for PRs is a bit confusing (for me at least).

      Is build 7 (in the screenshot) building all that commits? Why are there in different lines if it is the same build? Am I missing something?

      Screenshot taken from jenkins on jenkins instance.

          [JENKINS-38891] Pull Requests page is confusing

          Cliff Meyers added a comment -

          My 2 cents: probably needs an identifier for the pull request ID but really the branch name would probably be the most useful.

          Cliff Meyers added a comment - My 2 cents: probably needs an identifier for the pull request ID but really the branch name would probably be the most useful.

          Yeah, I agree cliffmeyers

          Thorsten Scherler added a comment - Yeah, I agree cliffmeyers

          Michael Neale added a comment -

          ah yes, this is to make you appear more productive and have more pull requests yeah this does seem wrong. I think what happens is that when there are multiple commits from multiple people they show up like this. amuniz can you link to some actual PRs this lists, so we can confirm?

          Michael Neale added a comment - ah yes, this is to make you appear more productive and have more pull requests yeah this does seem wrong. I think what happens is that when there are multiple commits from multiple people they show up like this. amuniz can you link to some actual PRs this lists, so we can confirm?

          Thorsten Scherler added a comment - michaelneale https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/pr

          Michael Neale added a comment -

          tscherler you mentioned that you didn't think was a bug - can you explain what is going on? (I am confused)

          Michael Neale added a comment - tscherler you mentioned that you didn't think was a bug - can you explain what is going on? (I am confused)

          michaelneale it is not a bug since AFAIR what we see is the original design, but could not found the old ticket tough. Anyway IMO we should simply add another column so we show the branch of the PR

          Thorsten Scherler added a comment - michaelneale it is not a bug since AFAIR what we see is the original design, but could not found the old ticket tough. Anyway IMO we should simply add another column so we show the branch of the PR

          Michael Neale added a comment -

          tscherler thanks - I will bug james about it when he is back (this isn't something I have looked at much), as it seems not what I would expect either.

          Michael Neale added a comment - tscherler thanks - I will bug james about it when he is back (this isn't something I have looked at much), as it seems not what I would expect either.

          Cliff Meyers added a comment -

          These are the current columns (in case the screenie doesn't make it clear): last build's status, build number, last commit message, author, last build completed, (action buttons)

          Cliff Meyers added a comment - These are the current columns (in case the screenie doesn't make it clear): last build's status, build number, last commit message, author, last build completed, (action buttons)

          James Dumay added a comment -

          What I think we should do here is drop the "Latest build" column and replace with a "Pull Request" ID and "Branch" column. WDYT?

          James Dumay added a comment - What I think we should do here is drop the "Latest build" column and replace with a "Pull Request" ID and "Branch" column. WDYT?

          Michael Neale added a comment -

          Thanks Antonio! I have rewritten this as a fresh ticket with actions to take

          Michael Neale added a comment - Thanks Antonio! I have rewritten this as a fresh ticket with actions to take

            Unassigned Unassigned
            amuniz Antonio Muñiz
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: