• Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Trivial Trivial
    • core
    • None
    • Platform: All, OS: All

      I attach a description to a particular build. Then, later I try to find out
      which build I edited: I have to browse through all build pages, because there is
      no hint regarding descriptions in the build history table of the project page.
      So this description feature has not the expected value (to me).

      It would be nice to see an icon that says "there is a descripton". Or you could
      show the first words of the description text. (rendered html?)

          [JENKINS-148] show (part of) description in build history

          vsizikov added a comment -

          Indeed, that functionality would be useful.

          vsizikov added a comment - Indeed, that functionality would be useful.

          vsizikov added a comment -

          Created an attachment (id=22)
          Build description is shown in build history, in full, but wrapped

          vsizikov added a comment - Created an attachment (id=22) Build description is shown in build history, in full, but wrapped

          vsizikov added a comment -

          Created an attachment (id=23)
          Build description is shown in build history, truncated

          vsizikov added a comment - Created an attachment (id=23) Build description is shown in build history, truncated

          vsizikov added a comment -

          After using modified Hudson for a day or so, I like "description with wrapping"
          much better. Truncation is too harsh and doesn't look goo to my eyes.

          If only I knew how to limit description in build history to some length, to
          avoid problems with very, very long descriptions. I think, about 100 letters to
          be shown in build history would be quite enough.

          vsizikov added a comment - After using modified Hudson for a day or so, I like "description with wrapping" much better. Truncation is too harsh and doesn't look goo to my eyes. If only I knew how to limit description in build history to some length, to avoid problems with very, very long descriptions. I think, about 100 letters to be shown in build history would be quite enough.

          What if we make it a tool tip that hovers?

          Or by default making it truncated, and if the mouse hovers, show the full text?

          Kohsuke Kawaguchi added a comment - What if we make it a tool tip that hovers? Or by default making it truncated, and if the mouse hovers, show the full text?

          vsizikov added a comment -

          Well, if somebody is trying to find all the builds with manual descriptions, a
          tooltip will not his/hers life much easier. While at least one line of truncated
          description (and a tooltip with full description) could be more suitable.

          But to me the truncated description does not look good, with cut right at the
          middle of the letter, for example.

          I guess, people use manual description in builds quite rare, and such
          descriptions deserve to be present in the build history, in more prominent role.

          Ideal solution for me would be a multi-line description not more than 4 lines of
          text, but it's not easy to do in the View (to limit the string), but maybe it
          would be simple to do in the model....

          vsizikov added a comment - Well, if somebody is trying to find all the builds with manual descriptions, a tooltip will not his/hers life much easier. While at least one line of truncated description (and a tooltip with full description) could be more suitable. But to me the truncated description does not look good, with cut right at the middle of the letter, for example. I guess, people use manual description in builds quite rare, and such descriptions deserve to be present in the build history, in more prominent role. Ideal solution for me would be a multi-line description not more than 4 lines of text, but it's not easy to do in the View (to limit the string), but maybe it would be simple to do in the model....

          OK, I don't feel strongly about tool tips, so we can forget that.

          Truncation algorithm could be smarter, like looking for the space character, etc.
          Feel free to implement this in the model, like getTruncatedDescription() or
          whatever.

          The other option is to write a groovy tag file and implement it there, then use
          existing buildHistory.jelly to use it. But I really don't mind having methods
          like that in the model code.

          Kohsuke Kawaguchi added a comment - OK, I don't feel strongly about tool tips, so we can forget that. Truncation algorithm could be smarter, like looking for the space character, etc. Feel free to implement this in the model, like getTruncatedDescription() or whatever. The other option is to write a groovy tag file and implement it there, then use existing buildHistory.jelly to use it. But I really don't mind having methods like that in the model code.

          vsizikov added a comment -

          will continue to work in this

          vsizikov added a comment - will continue to work in this

          vsizikov added a comment -

          The issue has been fixed as recommended by Kohsuke, with
          getTruncatedDescription in hudson.model.Run and truncation on spaces if the
          description is too long.

          vsizikov added a comment - The issue has been fixed as recommended by Kohsuke, with getTruncatedDescription in hudson.model.Run and truncation on spaces if the description is too long.

          gradopado added a comment -

          Thanks for the enhancement!

          verified with 1.67

          gradopado added a comment - Thanks for the enhancement! verified with 1.67

            vsizikov vsizikov
            gradopado gradopado
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: