The build pipeline doesn't display correctly. It is pushed to the right and the inner contents overflow the grey background container.

        1. Screen Shot 2015-11-05 at 2.54.27 PM.png
          Screen Shot 2015-11-05 at 2.54.27 PM.png
          112 kB
        2. BPP-1.4.8_1366px.png
          BPP-1.4.8_1366px.png
          63 kB
        3. BPP-1.4.8_1280px.png
          BPP-1.4.8_1280px.png
          64 kB
        4. BPL-1.4.8_1024px.png
          BPL-1.4.8_1024px.png
          63 kB
        5. version1_4_8_long.PNG
          version1_4_8_long.PNG
          63 kB
        6. version1_4_8_short.PNG
          version1_4_8_short.PNG
          25 kB
        7. display-inline.png
          display-inline.png
          56 kB
        8. Screen Shot 2015-07-17 at 10.17.57 AM.png
          Screen Shot 2015-07-17 at 10.17.57 AM.png
          148 kB

          [JENKINS-29477] View bad for Build Pipeline Plugin

          Phillip K. added a comment - - edited

          Hello Michael,
          i used this workaround:

          Copy following css rule into JENKINS_HOME/plugins/build-pipeline/css/main.css

          #main-panel{
          margin-left:0px;
          display: inline-block;
          }

          Phillip K. added a comment - - edited Hello Michael, i used this workaround: Copy following css rule into JENKINS_HOME/plugins/build-pipeline/css/main.css #main-panel{ margin-left:0px; display: inline-block; }

          John Wynne added a comment -

          Hey Phillip, I tried the same as you (without the 'display: inline-block' part) and it seems to be working. This should be used for resolution

          John Wynne added a comment - Hey Phillip, I tried the same as you (without the 'display: inline-block' part) and it seems to be working. This should be used for resolution

          Phillip K. added a comment -

          Hey John,
          the display attribute is needed to prevent the the overflow of the box.

          Phillip K. added a comment - Hey John, the display attribute is needed to prevent the the overflow of the box.

          John Wynne added a comment -

          Hey Philip, cheers for the reply! With 'display:inline-block' included, it does prevent overflow of the parent box as you said. However it also adds a big margin (equal in size to that in the description) to the right hand side of the page (see attached 'display-inline.jpg' . Do you see similar behaviour?

          John Wynne added a comment - Hey Philip, cheers for the reply! With 'display:inline-block' included, it does prevent overflow of the parent box as you said. However it also adds a big margin (equal in size to that in the description) to the right hand side of the page (see attached 'display-inline.jpg' . Do you see similar behaviour?

          Phillip K. added a comment -

          Hey John!
          I only tested the the css with overflowing content. Inline-block apdapts its size to the size of its content. Sorry for that!
          This modified rule should remove the left margin, prevent overflowing content and expand the box to at least the width of your screen. I tested it with Firefox only.

          #main-panel{
          margin-left:0px;
          display: inline-block;
          min-width:100%;
          }

          I'm not an active github user, so i will not promise anything, but i will try to get this modification into the repo.

          Phillip K. added a comment - Hey John! I only tested the the css with overflowing content. Inline-block apdapts its size to the size of its content. Sorry for that! This modified rule should remove the left margin, prevent overflowing content and expand the box to at least the width of your screen. I tested it with Firefox only. #main-panel{ margin-left:0px; display: inline-block; min-width:100%; } I'm not an active github user, so i will not promise anything, but i will try to get this modification into the repo.

          John Wynne added a comment - - edited

          Thanks a million Phillip!
          That's fixed it alright!
          I agree that your solution should be the resolution for this ticket:

          margin-left:0px; display: inline-block; min-width:100%;

          I'm not active with git either and am quite new to this, but cheers for your help!

          John Wynne added a comment - - edited Thanks a million Phillip! That's fixed it alright! I agree that your solution should be the resolution for this ticket: margin-left:0px; display: inline-block; min-width:100%; I'm not active with git either and am quite new to this, but cheers for your help!

          johnwynne, b0rengar, there is a new version of Build Pipeline Plugin. Could you try it and check if the problem still is present?

          Manuel Recena Soto added a comment - johnwynne , b0rengar , there is a new version of Build Pipeline Plugin. Could you try it and check if the problem still is present?

          Phillip K. added a comment -

          Screenshots of current Version 1.4.8. IMHO it looks even worse.

          Phillip K. added a comment - Screenshots of current Version 1.4.8. IMHO it looks even worse.

          b0rengar

          I understand. I'm going to re-open JENKINS-28180 and review the current implementation. It is important to keep in mind:

          1. If we use a liquid layout and we have several boxes (jobs) the expected result can see in the last screenshots.
          2. If we use fixed-with boxes and we have several boxes (jobs) the expected result will be a horizontal scrollbar.

          I'm going to work on it.

          Manuel Recena Soto added a comment - b0rengar I understand. I'm going to re-open JENKINS-28180 and review the current implementation. It is important to keep in mind: If we use a liquid layout and we have several boxes (jobs) the expected result can see in the last screenshots. If we use fixed-with boxes and we have several boxes (jobs) the expected result will be a horizontal scrollbar. I'm going to work on it.

          Manuel Recena Soto added a comment - - edited

          b0rengar

          Did you clean your browser cache? I get different screenshots.

          I've used the most popular screen resolutions and a pipeline with 6 steps:

          1. 1024px:
          2. 1280px:
          3. 1366px:

          What do you thing?

          Manuel Recena Soto added a comment - - edited b0rengar Did you clean your browser cache? I get different screenshots. I've used the most popular screen resolutions and a pipeline with 6 steps: 1024px: 1280px: 1366px: What do you thing?

          Phillip K. added a comment -

          Hey Manuel,
          my screen resolution is 1280x1024. I'm using Firefox 39.0. I did not clean my browser cache, but i edited css on the fly with out problems.
          My personal opinion for the layout ( ">" stands for "better than"):
          Big Screen > Scrolling > Overflowing content > too small to read

          P.s.: You may noticed in my screenshots, i tried to fork and rejoin the jobs of the build pipeline. The execution of the jobs works as ecpected but the visulisation (especially of the rejoin) could be better. Are you aware of this Problem? Should I create a new ticket for this issue?

          Phillip K. added a comment - Hey Manuel, my screen resolution is 1280x1024. I'm using Firefox 39.0. I did not clean my browser cache, but i edited css on the fly with out problems. My personal opinion for the layout ( ">" stands for "better than"): Big Screen > Scrolling > Overflowing content > too small to read P.s.: You may noticed in my screenshots, i tried to fork and rejoin the jobs of the build pipeline. The execution of the jobs works as ecpected but the visulisation (especially of the rejoin) could be better. Are you aware of this Problem? Should I create a new ticket for this issue?

          b0rengar

          This proposal involves changes (important) if we want to do in a right way. In my opinion, the priority is to decide with layout we want for this UI (liquid, fixed-width boxes). It is clear than if you have a lot of builds (steps) the only option is horizontal scrollbar.

          The bug described in this ticket is solved with the current implementation (1.4.8). Isn't that so?

          Manuel Recena Soto added a comment - b0rengar This proposal involves changes (important) if we want to do in a right way. In my opinion, the priority is to decide with layout we want for this UI (liquid, fixed-width boxes). It is clear than if you have a lot of builds (steps) the only option is horizontal scrollbar. The bug described in this ticket is solved with the current implementation (1.4.8). Isn't that so?

          Phillip K. added a comment -

          No the bug is still there in my Enviroment! Maybe John Wynne could test it to have second test result.
          I just noticed in your Screenshot that your Jenkins version is 1.554.3. My Jenkins version 1.628 and the Version of the original creator of this issue is 1.619. I think you should update your Jenkins to be able to reproduce this bug.

          For the ui: it would be nice to have growing/shrinking boxes dependend on the screen size, but it is important that the content is always readable and overflowing is prevented, everything else is just nice to have.

          Phillip K. added a comment - No the bug is still there in my Enviroment! Maybe John Wynne could test it to have second test result. I just noticed in your Screenshot that your Jenkins version is 1.554.3. My Jenkins version 1.628 and the Version of the original creator of this issue is 1.619. I think you should update your Jenkins to be able to reproduce this bug. For the ui: it would be nice to have growing/shrinking boxes dependend on the screen size, but it is important that the content is always readable and overflowing is prevented, everything else is just nice to have.

          b0rengar Ok, I'll work on it and share the result here. Do you agree?

          Manuel Recena Soto added a comment - b0rengar Ok, I'll work on it and share the result here. Do you agree?

          Phillip K. added a comment -

          I don't think you need my Permission or Agreement , but if you want it: I agree with you

          Phillip K. added a comment - I don't think you need my Permission or Agreement , but if you want it: I agree with you

          Yariv Sheizaf added a comment -

          Hello Manuel,
          Is there any promotion regarding this issue?

          Yariv Sheizaf added a comment - Hello Manuel, Is there any promotion regarding this issue?

          yarivs I hope having time to jump here soon

          Manuel Recena Soto added a comment - yarivs I hope having time to jump here soon

          Yariv Sheizaf added a comment -

          Thx !

          Yariv Sheizaf added a comment - Thx !

          I think the only viable option for large pipelines is fixed width boxes.

          Daniel Serodio added a comment - I think the only viable option for large pipelines is fixed width boxes.

          Gustavo Souza added a comment - - edited

          My build pipeline has 6 jobs and the view is completely messed up.. The view´s div is aligned on the right and it does not use the full width of my screen

          I am using build pipeline plugin v 1.4.8

          Gustavo Souza added a comment - - edited My build pipeline has 6 jobs and the view is completely messed up.. The view´s div is aligned on the right and it does not use the full width of my screen I am using build pipeline plugin v 1.4.8

          Code changed in jenkins
          User: Fishermans
          Path:
          src/main/webapp/css/main.css
          http://jenkins-ci.org/commit/build-pipeline-plugin/d8eb803c054b30a7c423ad543f5433316ee6f81a
          Log:

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Fishermans Path: src/main/webapp/css/main.css http://jenkins-ci.org/commit/build-pipeline-plugin/d8eb803c054b30a7c423ad543f5433316ee6f81a Log: Fixed JENKINS-29477

          Code changed in jenkins
          User: Dan Alvizu
          Path:
          src/main/webapp/css/main.css
          http://jenkins-ci.org/commit/build-pipeline-plugin/b5d8f5251bcf1c9c1711e1d9513bd0dc66911629
          Log:
          Merge pull request #92 from fishermans/master

          [Fixed JENKINS-29477]

          Compare: https://github.com/jenkinsci/build-pipeline-plugin/compare/77a1a2ffa368...b5d8f5251bcf

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Dan Alvizu Path: src/main/webapp/css/main.css http://jenkins-ci.org/commit/build-pipeline-plugin/b5d8f5251bcf1c9c1711e1d9513bd0dc66911629 Log: Merge pull request #92 from fishermans/master [Fixed JENKINS-29477] Compare: https://github.com/jenkinsci/build-pipeline-plugin/compare/77a1a2ffa368...b5d8f5251bcf

          Yariv Sheizaf added a comment -

          Hi,

          I installed the new main.css code. The size and content of the job names and information is now correct.
          The problem is that the standard main frame horizontal scroll does not exist anymore.
          So, navigation can be done using one of two alternatives:
          1. Using keyboard arrows.
          2. using the internal horizontal scroll which is semi hidden and does not useful if I have a big pipeline or want to see more than the latest build process.

          Yariv Sheizaf added a comment - Hi, I installed the new main.css code. The size and content of the job names and information is now correct. The problem is that the standard main frame horizontal scroll does not exist anymore. So, navigation can be done using one of two alternatives: 1. Using keyboard arrows. 2. using the internal horizontal scroll which is semi hidden and does not useful if I have a big pipeline or want to see more than the latest build process.

          yarivs, Please, file a new issue.

          Manuel Recena Soto added a comment - yarivs , Please, file a new issue.

          Resolved by https://github.com/fishermans with this PR.

          Manuel Recena Soto added a comment - Resolved by https://github.com/fishermans with this PR .

            recena Manuel Recena Soto
            mscharp Michael Scharp
            Votes:
            6 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: