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

UI: Build History box looks bad with medium to long build labels

      The build history box allocates about 50% of its width to the build label and about 50% to the build time. This often means that the build label wraps after the status icon.

      The simplest solution would be to define the style:
      #buildHistory .build-name {
      /* max-width: 120px; */
      white-space: nowrap;
      }

      Along with that it would be good to either make the build time use a smaller font size or use a format for the date that takes less space or use a different date format based on how long ago the build was.

          [JENKINS-25393] UI: Build History box looks bad with medium to long build labels

          This problem first occurred in 1.580.1 and seems to be an outgrowth of this set of issues.

          Paul Mendelson added a comment - This problem first occurred in 1.580.1 and seems to be an outgrowth of this set of issues.

          Daniel Beck added a comment -

          May even be a duplicate of JENKINS-25381.

          Daniel Beck added a comment - May even be a duplicate of JENKINS-25381 .

          Please, fix or escalate this issue. It is not minor! The Build History is a central launch point and in 1.580.1 its display is a mess. Attaching a screen shot.

          Ioannis Moutsatsos added a comment - Please, fix or escalate this issue. It is not minor! The Build History is a central launch point and in 1.580.1 its display is a mess. Attaching a screen shot.

          This screenshot demonstrates how difficult it is to find the build link with a hyman readable build name and description

          Ioannis Moutsatsos added a comment - This screenshot demonstrates how difficult it is to find the build link with a hyman readable build name and description

          Daniel Beck added a comment -

          FYI this is currently being worked on e.g. here: https://github.com/jenkinsci/jenkins/pull/1466

          Note that it looks like you're using the build name to describe it... maybe use the description field for that instead?

          Daniel Beck added a comment - FYI this is currently being worked on e.g. here: https://github.com/jenkinsci/jenkins/pull/1466 Note that it looks like you're using the build name to describe it... maybe use the description field for that instead?

          Tom FENNELLY added a comment -

          Please see https://github.com/jenkinsci/jenkins/pull/1470. Try it if you can and provide feedback.

          Tom FENNELLY added a comment - Please see https://github.com/jenkinsci/jenkins/pull/1470 . Try it if you can and provide feedback.

          Tom FENNELLY added a comment -

          Fixed in cb9036c45527223525cc1b48020a8ed777020c1a

          Tom FENNELLY added a comment - Fixed in cb9036c45527223525cc1b48020a8ed777020c1a

          Ioannis Moutsatsos added a comment - - edited

          This look really nice in 1.593! Thank you for fixing this. Although it might have looked as I have been using descriptions for build names, this is is not the case. Our build names are indeed long since they have to reflect the workflow that a data set we are analyzing has gone through. I'm very pleased with you current implementation. I hope it gets rolled into an LTS release soon!

          Ioannis Moutsatsos added a comment - - edited This look really nice in 1.593! Thank you for fixing this. Although it might have looked as I have been using descriptions for build names, this is is not the case. Our build names are indeed long since they have to reflect the workflow that a data set we are analyzing has gone through. I'm very pleased with you current implementation. I hope it gets rolled into an LTS release soon!

            Unassigned Unassigned
            mendelson_paulh Paul Mendelson
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: