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

Provide links for all tabs in details page

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: warnings-plugin
    • Labels:
    • Environment:
      Warnings Plug-in 4.68
      Jenkins ver. 2.138.1
      MacOS 10.13.6 17G65
      Safari 11.1.2 (13605.3.8)
      Also Chrome 66.0.3359.181 (Official Build) (64-bit)
    • Similar Issues:
    • Released As:
      5.0.0-beta3

      Description

      The tabs in a build’s LLVM/Clang Warnings page Details section (Folders, Files, People etc.) all have associated URLs, which can be copied by right-clicking on one of the tabs and selecting “Copy Link.”  But the URL doesn’t actually work; they all seem to end in a “#” with no associated anchor, e.g.: http…/job/…/7/warnings10Result/#

          I would like to post the People link as part of our notification when a build has warnings; it seems a better motivator than the default tab, Folders.

          Thanks, by the way, for a magnificent plugin which is raising the visibility of compiler warnings and (should they ever occur) sanitizer run-time failures.

        Attachments

          Activity

          Hide
          drulli Ulli Hafner added a comment -

          Added support for URL switching in upcoming 5.0 release, see #2547d29.

          So once the Git blame functionality is integrated into the 5.0 release (still under development) it should be available.

          Show
          drulli Ulli Hafner added a comment - Added support for URL switching in upcoming 5.0 release, see #2547d29 . So once the Git blame functionality is integrated into the 5.0 release (still under development ) it should be available.
          Hide
          flasheridn Flash Sheridan added a comment -

          Thanks very much; I had to upgrade to 5.0ß today for a new Pipeline project, so that will suffice for us.  (The backward compatibility for a non-Pipeline build seemed fine, by the way—the only difference I’ve noticed so far was the Deprecated label.  I do prefer the old non-Pipeline appearance though; it’s more information-rich, with things like New and Fixed numbers prominently displayed.)

           

          Show
          flasheridn Flash Sheridan added a comment - Thanks very much; I had to upgrade to 5.0ß today for a new Pipeline project, so that will suffice for us.  (The backward compatibility for a non-Pipeline build seemed fine, by the way—the only difference I’ve noticed so far was the Deprecated label.  I do prefer the old non-Pipeline appearance though; it’s more information-rich, with things like New and Fixed numbers prominently displayed.)  
          Hide
          drulli Ulli Hafner added a comment -

          I'm not sure if I understand correctly. Pipelines and Freestyle projects in 5.x have the same UI. Which UI do you prefer exactly?

          Show
          drulli Ulli Hafner added a comment - I'm not sure if I understand correctly. Pipelines and Freestyle projects in 5.x have the same UI. Which UI do you prefer exactly?
          Hide
          flasheridn Flash Sheridan added a comment -

          I really like the beginning of the Clang Warnings page (below, deliberately truncated), with New and Fixed Warnings prominently displayed:

           The beginning of the CheckStyle (in our case actually Scala Style) page is less informative:

           

           

           

          Show
          flasheridn Flash Sheridan added a comment - I really like the beginning of the Clang Warnings page (below, deliberately truncated), with New and Fixed Warnings prominently displayed:  The beginning of the CheckStyle (in our case actually Scala Style) page is less informative:      
          Hide
          drulli Ulli Hafner added a comment -

          I see, seems that you are using the wrong post build action for the Clang warnings. You should use the same post build action as for CheckStyle. When you click on the arrow, you will see a chart for new warnings as well.

          Does it make sense to see the new warnings as first chart in the carousel? Or should I save the selected chart so you get the same selection if you open the page again?

          Show
          drulli Ulli Hafner added a comment - I see, seems that you are using the wrong post build action for the Clang warnings. You should use the same post build action as for CheckStyle. When you click on the arrow, you will see a chart for new warnings as well. Does it make sense to see the new warnings as first chart in the carousel? Or should I save the selected chart so you get the same selection if you open the page again?
          Hide
          flasheridn Flash Sheridan added a comment -

          Saving the last selection strikes me as good UI, but I really do prefer the old text-heavy UI (from the non-Pipeline project) to the new graphics, enough that I’ve created a non-Pipeline build for our Scala Style build as well.

          Show
          flasheridn Flash Sheridan added a comment - Saving the last selection strikes me as good UI, but I really do prefer the old text-heavy UI (from the non-Pipeline project) to the new graphics, enough that I’ve created a non-Pipeline build for our Scala Style build as well.
          Hide
          drulli Ulli Hafner added a comment -

          Will be part of beta2.

          Show
          drulli Ulli Hafner added a comment - Will be part of beta2.

            People

            Assignee:
            drulli Ulli Hafner
            Reporter:
            flasheridn Flash Sheridan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: