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

Layout: Build executor status overlap main pane when job-weight > 1

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • core
    • Jenkins LTS ver. 1.580.1
      Jenkins LTS ver. 1.580.2
      Jenkins LTS ver. 1.651.1

      Layout: Build executor status may overlap main pane for jobs with a long name and job-weight > 1
      When the "Occupied by" text appears, the jobname is not wraped to fit in the table.

      See screenshot.

      Maybe same problem as https://issues.jenkins-ci.org/browse/JENKINS-23829

      How to reproduce:
      1. create a job with a long name to run on slave "x"
      2. have a slave "x" with 4 executors
      3. set "Job Weight = 4"
      4. run the job

        1. build-executor-status_wrapped-correctly.PNG
          build-executor-status_wrapped-correctly.PNG
          7 kB
        2. build-executor-status-not_wrapped-correctly.PNG
          build-executor-status-not_wrapped-correctly.PNG
          15 kB
        3. Screen Shot 2016-05-27 at 10.20.52.png
          Screen Shot 2016-05-27 at 10.20.52.png
          39 kB

          [JENKINS-26177] Layout: Build executor status overlap main pane when job-weight > 1

          Daniel Beck added a comment -

          Different widget. The builds history got some work done in 1.593(ish), maybe that can be transferred to the executors list as well?

          Would also be nice if you could reproduce this behavior with the latest weekly release to make sure it hasn't been fixed since 1.580.

          Daniel Beck added a comment - Different widget. The builds history got some work done in 1.593(ish), maybe that can be transferred to the executors list as well? Would also be nice if you could reproduce this behavior with the latest weekly release to make sure it hasn't been fixed since 1.580.

          ralf oyen added a comment -

          I can reproduce this with Jenkins ver. 1.595, same problem.

          ralf oyen added a comment - I can reproduce this with Jenkins ver. 1.595, same problem.

          Victor Martinez added a comment -

          I've seen that issue in different jenkins instances, and actually in the previous latest one:
          Jenkins LTS ver. 1.651.1

          Cheers

          Victor Martinez added a comment - I've seen that issue in different jenkins instances, and actually in the previous latest one: Jenkins LTS ver. 1.651.1 Cheers

            Unassigned Unassigned
            ralf_o ralf oyen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: