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

Multi-branch pipeline status icon no longer shows worst status of jobs in that multi-branch 'folder'

    Details

    • Similar Issues:

      Description

      The status icon of multi-branch pipeline jobs in a folder could optionally be adjusted to show the status of the worst job in that multi-branch pipeline as the status for that multi-branch pipeline. Recent updates to plugins have changed that behavior so it no longer shows worst status.

      Steps to see the expected behavior (before the change):

      1. Clone my docker instance and checkout the JENKINS-41785-before tag
          $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-before
          $ cd JENKINS-41785-before
          $ git checkout -b JENKINS-41785-before JENKINS-41785-before
        
      2. Build and run the docker instance
          $ docker build -t jenkins:JENKINS-41785-before .
          $ docker run -i --rm --publish 8080:8080 --publish 50000:50000 --publish 18022:18022 -t jenkins:JENKINS-41785-before
        
      3. Open a web browser to that running docker instance
      4. Open the "Bugs - Pipeline Checks" folder
      5. Observe the icon for the jenkins-bugs multi-branch pipeline folder
      6. Open the jenkins-bugs multi-branch pipeline folder and index the branches
      7. Wait until at least one of the pipeline jobs completes
      8. Navigate to the "Bus - Pipeline Checks" folder and confirm the status is correct

      Steps to see the unexpected (changed) behavior:

      1. Clone my docker instance and checkout the JENKINS-41785-after tag
          $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-after
          $ cd JENKINS-41785-after
          $ git checkout -b JENKINS-41785-after JENKINS-41785-after
        
      2. Build and run the docker instance
          $ docker build -t jenkins:JENKINS-41785-after .
          $ docker run -i --rm --publish 8080:8080 --publish 50000:50000 --publish 18022:18022 -t jenkins:JENKINS-41785-after
        
      3. Open a web browser to that running docker instance
      4. Open the "Bugs - Pipeline Checks" folder
      5. Observe the icon for the jenkins-bugs multi-branch pipeline folder is incorrect (shows no status)
      6. Open the jenkins-bugs multi-branch pipeline folder and index the branches
      7. Wait until at least one of the pipeline jobs completes
      8. Navigate to the "Bus - Pipeline Checks" folder and confirm the status is still incorrect (shows no status)

      The parent folder does still show the "worst status" when it is configured (see ). It seems to only be the pipeline folder that is unable to show worst case status. This might be related to JENKINS-40545, since I see a null pointer exception reported when I try to configure that pipeline job in the folder, though the null pointer exception also appears when I configure a folder in a folder.

        Attachments

          Activity

          markewaite Mark Waite created issue -
          mjdetullio Matthew DeTullio made changes -
          Field Original Value New Value
          Component/s workflow-multibranch-plugin [ 21465 ]
          Component/s multi-branch-project-plugin [ 21127 ]
          mjdetullio Matthew DeTullio made changes -
          Assignee Matthew DeTullio [ mjdetullio ]
          markewaite Mark Waite made changes -
          markewaite Mark Waite made changes -
          markewaite Mark Waite made changes -
          markewaite Mark Waite made changes -
          Description The status icon of multi-branch pipeline jobs in a folder could optionally be adjusted to show the status of the worst job in that multi-branch pipeline as the status for that multi-branch pipeline. Recent updates to plugins have changed that behavior so it no longer shows worst status.

          Steps to see the expected behavior (before the change):

          # Clone my docker instance and checkout the xx tag
          # Build the docker instance
          # Run the docker instance
          # Open a web browser to that running docker instance
          # Open the "Bugs - Pipeline Checks" folder
          # Observe the icon for the jenkins-bugs multi-branch pipeline folder
          # Open the jenkins-bugs multi-branch pipeline folder and index the branches
          # Wait until at least one of the pipeline jobs completes
          # Navigate to the "Bus - Pipeline Checks" folder and confirm the status is correct

          Steps to see the unexpected (changed) behavior:

          # Clone my docker instance and checkout the yy tag
          # Build the docker instance
          # Run the docker instance
          # Open a web browser to that running docker instance
          # Open the "Bugs - Pipeline Checks" folder
          # Observe the icon for the jenkins-bugs multi-branch pipeline folder is incorrect
          # Open the jenkins-bugs multi-branch pipeline folder and index the branches
          # Wait until at least one of the pipeline jobs completes
          # Navigate to the "Bus - Pipeline Checks" folder and confirm the status is incorrect
          The status icon of multi-branch pipeline jobs in a folder could optionally be adjusted to show the status of the worst job in that multi-branch pipeline as the status for that multi-branch pipeline. Recent updates to plugins have changed that behavior so it no longer shows worst status.

          Steps to see the expected behavior (before the change):

          # Clone my docker instance and checkout the JENKINS-41785-before tag
          {code}
            $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-before
            $ cd JENKINS-41785-before
            $ git checkout -b JENKINS-41785-before JENKINS-41785-before
          {code}
          # Build and run the docker instance
          {code}
            $ docker build -t jenkins:JENKINS-41785-before .
            $ docker run -i --rm --publish 8080:8080 --publish 50000:50000 --publish 18022:18022 -t jenkins:JENKINS-41785-before
          {code}
          # Open a web browser to that running docker instance
          # Open the "Bugs - Pipeline Checks" folder
          # Observe the icon for the jenkins-bugs multi-branch pipeline folder
          # Open the jenkins-bugs multi-branch pipeline folder and index the branches
          # Wait until at least one of the pipeline jobs completes
          # Navigate to the "Bus - Pipeline Checks" folder and confirm the status is correct

          Steps to see the unexpected (changed) behavior:

          # Clone my docker instance and checkout the JENKINS-41785-after tag
          {code}
            $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-after
            $ cd JENKINS-41785-after
            $ git checkout -b JENKINS-41785-after JENKINS-41785-after
          {code}
          # Build and run the docker instance
          {code}
            $ docker build -t jenkins:JENKINS-41785-after .
            $ docker run -i --rm --publish 8080:8080 --publish 50000:50000 --publish 18022:18022 -t jenkins:JENKINS-41785-after
          {code}
          # Open a web browser to that running docker instance
          # Open the "Bugs - Pipeline Checks" folder
          # Observe the icon for the jenkins-bugs multi-branch pipeline folder is incorrect (shows no status) (see !Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail!
          # Open the jenkins-bugs multi-branch pipeline folder and index the branches
          # Wait until at least one of the pipeline jobs completes
          # Navigate to the "Bus - Pipeline Checks" folder and confirm the status is still incorrect (shows no status) !Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail! !parent-folder-configured-show-aggregate-ball-color-status.PNG|thumbnail! !parent-folder-shows-correct-aggregate-color.PNG|thumbnail!

          The parent folder does still show the "worst status" when it is configured (see !parent-folder-shows-correct-aggregate-color.PNG|thumbnail! ). It seems to only be the pipeline folder that is unable to show worst case status. This might be related to JENKINS-40545, since I see a null pointer exception reported when I try to configure that pipeline job in the folder, though the null pointer exception also appears when I configure a folder in a folder.
          markewaite Mark Waite made changes -
          Description The status icon of multi-branch pipeline jobs in a folder could optionally be adjusted to show the status of the worst job in that multi-branch pipeline as the status for that multi-branch pipeline. Recent updates to plugins have changed that behavior so it no longer shows worst status.

          Steps to see the expected behavior (before the change):

          # Clone my docker instance and checkout the JENKINS-41785-before tag
          {code}
            $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-before
            $ cd JENKINS-41785-before
            $ git checkout -b JENKINS-41785-before JENKINS-41785-before
          {code}
          # Build and run the docker instance
          {code}
            $ docker build -t jenkins:JENKINS-41785-before .
            $ docker run -i --rm --publish 8080:8080 --publish 50000:50000 --publish 18022:18022 -t jenkins:JENKINS-41785-before
          {code}
          # Open a web browser to that running docker instance
          # Open the "Bugs - Pipeline Checks" folder
          # Observe the icon for the jenkins-bugs multi-branch pipeline folder
          # Open the jenkins-bugs multi-branch pipeline folder and index the branches
          # Wait until at least one of the pipeline jobs completes
          # Navigate to the "Bus - Pipeline Checks" folder and confirm the status is correct

          Steps to see the unexpected (changed) behavior:

          # Clone my docker instance and checkout the JENKINS-41785-after tag
          {code}
            $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-after
            $ cd JENKINS-41785-after
            $ git checkout -b JENKINS-41785-after JENKINS-41785-after
          {code}
          # Build and run the docker instance
          {code}
            $ docker build -t jenkins:JENKINS-41785-after .
            $ docker run -i --rm --publish 8080:8080 --publish 50000:50000 --publish 18022:18022 -t jenkins:JENKINS-41785-after
          {code}
          # Open a web browser to that running docker instance
          # Open the "Bugs - Pipeline Checks" folder
          # Observe the icon for the jenkins-bugs multi-branch pipeline folder is incorrect (shows no status) (see !Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail!
          # Open the jenkins-bugs multi-branch pipeline folder and index the branches
          # Wait until at least one of the pipeline jobs completes
          # Navigate to the "Bus - Pipeline Checks" folder and confirm the status is still incorrect (shows no status) !Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail! !parent-folder-configured-show-aggregate-ball-color-status.PNG|thumbnail! !parent-folder-shows-correct-aggregate-color.PNG|thumbnail!

          The parent folder does still show the "worst status" when it is configured (see !parent-folder-shows-correct-aggregate-color.PNG|thumbnail! ). It seems to only be the pipeline folder that is unable to show worst case status. This might be related to JENKINS-40545, since I see a null pointer exception reported when I try to configure that pipeline job in the folder, though the null pointer exception also appears when I configure a folder in a folder.
          The status icon of multi-branch pipeline jobs in a folder could optionally be adjusted to show the status of the worst job in that multi-branch pipeline as the status for that multi-branch pipeline. Recent updates to plugins have changed that behavior so it no longer shows worst status.

          Steps to see the expected behavior (before the change):

          # Clone my docker instance and checkout the JENKINS-41785-before tag
          {code}
            $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-before
            $ cd JENKINS-41785-before
            $ git checkout -b JENKINS-41785-before JENKINS-41785-before
          {code}
          # Build and run the docker instance
          {code}
            $ docker build -t jenkins:JENKINS-41785-before .
            $ docker run -i --rm --publish 8080:8080 --publish 50000:50000 --publish 18022:18022 -t jenkins:JENKINS-41785-before
          {code}
          # Open a web browser to that running docker instance
          # Open the "Bugs - Pipeline Checks" folder
          # Observe the icon for the jenkins-bugs multi-branch pipeline folder
          # Open the jenkins-bugs multi-branch pipeline folder and index the branches
          # Wait until at least one of the pipeline jobs completes
          # Navigate to the "Bus - Pipeline Checks" folder and confirm the status is correct

          Steps to see the unexpected (changed) behavior:

          # Clone my docker instance and checkout the JENKINS-41785-after tag
          {code}
            $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-after
            $ cd JENKINS-41785-after
            $ git checkout -b JENKINS-41785-after JENKINS-41785-after
          {code}
          # Build and run the docker instance
          {code}
            $ docker build -t jenkins:JENKINS-41785-after .
            $ docker run -i --rm --publish 8080:8080 --publish 50000:50000 --publish 18022:18022 -t jenkins:JENKINS-41785-after
          {code}
          # Open a web browser to that running docker instance
          # Open the "Bugs - Pipeline Checks" folder
          # Observe the icon for the jenkins-bugs multi-branch pipeline folder is incorrect (shows no status)
            (see !Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail!
          # Open the jenkins-bugs multi-branch pipeline folder and index the branches
          # Wait until at least one of the pipeline jobs completes
          # Navigate to the "Bus - Pipeline Checks" folder and confirm the status is still incorrect (shows no status)
            See !Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail! !parent-folder-configured-show-aggregate-ball-color-status.PNG|thumbnail! !parent-folder-shows-correct-aggregate-color.PNG|thumbnail!

          The parent folder does still show the "worst status" when it is configured (see !parent-folder-shows-correct-aggregate-color.PNG|thumbnail! ). It seems to only be the pipeline folder that is unable to show worst case status. This might be related to JENKINS-40545, since I see a null pointer exception reported when I try to configure that pipeline job in the folder, though the null pointer exception also appears when I configure a folder in a folder.
          markewaite Mark Waite made changes -
          Description The status icon of multi-branch pipeline jobs in a folder could optionally be adjusted to show the status of the worst job in that multi-branch pipeline as the status for that multi-branch pipeline. Recent updates to plugins have changed that behavior so it no longer shows worst status.

          Steps to see the expected behavior (before the change):

          # Clone my docker instance and checkout the JENKINS-41785-before tag
          {code}
            $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-before
            $ cd JENKINS-41785-before
            $ git checkout -b JENKINS-41785-before JENKINS-41785-before
          {code}
          # Build and run the docker instance
          {code}
            $ docker build -t jenkins:JENKINS-41785-before .
            $ docker run -i --rm --publish 8080:8080 --publish 50000:50000 --publish 18022:18022 -t jenkins:JENKINS-41785-before
          {code}
          # Open a web browser to that running docker instance
          # Open the "Bugs - Pipeline Checks" folder
          # Observe the icon for the jenkins-bugs multi-branch pipeline folder
          # Open the jenkins-bugs multi-branch pipeline folder and index the branches
          # Wait until at least one of the pipeline jobs completes
          # Navigate to the "Bus - Pipeline Checks" folder and confirm the status is correct

          Steps to see the unexpected (changed) behavior:

          # Clone my docker instance and checkout the JENKINS-41785-after tag
          {code}
            $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-after
            $ cd JENKINS-41785-after
            $ git checkout -b JENKINS-41785-after JENKINS-41785-after
          {code}
          # Build and run the docker instance
          {code}
            $ docker build -t jenkins:JENKINS-41785-after .
            $ docker run -i --rm --publish 8080:8080 --publish 50000:50000 --publish 18022:18022 -t jenkins:JENKINS-41785-after
          {code}
          # Open a web browser to that running docker instance
          # Open the "Bugs - Pipeline Checks" folder
          # Observe the icon for the jenkins-bugs multi-branch pipeline folder is incorrect (shows no status)
            (see !Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail!
          # Open the jenkins-bugs multi-branch pipeline folder and index the branches
          # Wait until at least one of the pipeline jobs completes
          # Navigate to the "Bus - Pipeline Checks" folder and confirm the status is still incorrect (shows no status)
            See !Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail! !parent-folder-configured-show-aggregate-ball-color-status.PNG|thumbnail! !parent-folder-shows-correct-aggregate-color.PNG|thumbnail!

          The parent folder does still show the "worst status" when it is configured (see !parent-folder-shows-correct-aggregate-color.PNG|thumbnail! ). It seems to only be the pipeline folder that is unable to show worst case status. This might be related to JENKINS-40545, since I see a null pointer exception reported when I try to configure that pipeline job in the folder, though the null pointer exception also appears when I configure a folder in a folder.
          The status icon of multi-branch pipeline jobs in a folder could optionally be adjusted to show the status of the worst job in that multi-branch pipeline as the status for that multi-branch pipeline. Recent updates to plugins have changed that behavior so it no longer shows worst status.

          Steps to see the expected behavior (before the change):

          # Clone my docker instance and checkout the JENKINS-41785-before tag
          {code}
            $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-before
            $ cd JENKINS-41785-before
            $ git checkout -b JENKINS-41785-before JENKINS-41785-before
          {code}
          # Build and run the docker instance
          {code}
            $ docker build -t jenkins:JENKINS-41785-before .
            $ docker run -i --rm --publish 8080:8080 --publish 50000:50000 --publish 18022:18022 -t jenkins:JENKINS-41785-before
          {code}
          # Open a web browser to that running docker instance
          # Open the "Bugs - Pipeline Checks" folder
          # Observe the icon for the jenkins-bugs multi-branch pipeline folder
          # Open the jenkins-bugs multi-branch pipeline folder and index the branches
          # Wait until at least one of the pipeline jobs completes
          # Navigate to the "Bus - Pipeline Checks" folder and confirm the status is correct

          Steps to see the unexpected (changed) behavior:

          # Clone my docker instance and checkout the JENKINS-41785-after tag
          {code}
            $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-after
            $ cd JENKINS-41785-after
            $ git checkout -b JENKINS-41785-after JENKINS-41785-after
          {code}
          # Build and run the docker instance
          {code}
            $ docker build -t jenkins:JENKINS-41785-after .
            $ docker run -i --rm --publish 8080:8080 --publish 50000:50000 --publish 18022:18022 -t jenkins:JENKINS-41785-after
          {code}
          # Open a web browser to that running docker instance
          # Open the "Bugs - Pipeline Checks" folder
          # Observe the icon for the jenkins-bugs multi-branch pipeline folder is incorrect (shows no status)
            (see !Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail! )
          # Open the jenkins-bugs multi-branch pipeline folder and index the branches
          # Wait until at least one of the pipeline jobs completes
          # Navigate to the "Bus - Pipeline Checks" folder and confirm the status is still incorrect (shows no status)
            See !parent-folder-shows-correct-aggregate-color.PNG|thumbnail!

          The parent folder does still show the "worst status" when it is configured (see !parent-folder-shows-correct-aggregate-color.PNG|thumbnail! ). It seems to only be the pipeline folder that is unable to show worst case status. This might be related to JENKINS-40545, since I see a null pointer exception reported when I try to configure that pipeline job in the folder, though the null pointer exception also appears when I configure a folder in a folder.
          markewaite Mark Waite made changes -
          Description The status icon of multi-branch pipeline jobs in a folder could optionally be adjusted to show the status of the worst job in that multi-branch pipeline as the status for that multi-branch pipeline. Recent updates to plugins have changed that behavior so it no longer shows worst status.

          Steps to see the expected behavior (before the change):

          # Clone my docker instance and checkout the JENKINS-41785-before tag
          {code}
            $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-before
            $ cd JENKINS-41785-before
            $ git checkout -b JENKINS-41785-before JENKINS-41785-before
          {code}
          # Build and run the docker instance
          {code}
            $ docker build -t jenkins:JENKINS-41785-before .
            $ docker run -i --rm --publish 8080:8080 --publish 50000:50000 --publish 18022:18022 -t jenkins:JENKINS-41785-before
          {code}
          # Open a web browser to that running docker instance
          # Open the "Bugs - Pipeline Checks" folder
          # Observe the icon for the jenkins-bugs multi-branch pipeline folder
          # Open the jenkins-bugs multi-branch pipeline folder and index the branches
          # Wait until at least one of the pipeline jobs completes
          # Navigate to the "Bus - Pipeline Checks" folder and confirm the status is correct

          Steps to see the unexpected (changed) behavior:

          # Clone my docker instance and checkout the JENKINS-41785-after tag
          {code}
            $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-after
            $ cd JENKINS-41785-after
            $ git checkout -b JENKINS-41785-after JENKINS-41785-after
          {code}
          # Build and run the docker instance
          {code}
            $ docker build -t jenkins:JENKINS-41785-after .
            $ docker run -i --rm --publish 8080:8080 --publish 50000:50000 --publish 18022:18022 -t jenkins:JENKINS-41785-after
          {code}
          # Open a web browser to that running docker instance
          # Open the "Bugs - Pipeline Checks" folder
          # Observe the icon for the jenkins-bugs multi-branch pipeline folder is incorrect (shows no status)
            (see !Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail! )
          # Open the jenkins-bugs multi-branch pipeline folder and index the branches
          # Wait until at least one of the pipeline jobs completes
          # Navigate to the "Bus - Pipeline Checks" folder and confirm the status is still incorrect (shows no status)
            See !parent-folder-shows-correct-aggregate-color.PNG|thumbnail!

          The parent folder does still show the "worst status" when it is configured (see !parent-folder-shows-correct-aggregate-color.PNG|thumbnail! ). It seems to only be the pipeline folder that is unable to show worst case status. This might be related to JENKINS-40545, since I see a null pointer exception reported when I try to configure that pipeline job in the folder, though the null pointer exception also appears when I configure a folder in a folder.
          The status icon of multi-branch pipeline jobs in a folder could optionally be adjusted to show the status of the worst job in that multi-branch pipeline as the status for that multi-branch pipeline. Recent updates to plugins have changed that behavior so it no longer shows worst status.

          Steps to see the expected behavior (before the change):

          # Clone my docker instance and checkout the JENKINS-41785-before tag
          {code}
            $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-before
            $ cd JENKINS-41785-before
            $ git checkout -b JENKINS-41785-before JENKINS-41785-before
          {code}
          # Build and run the docker instance
          {code}
            $ docker build -t jenkins:JENKINS-41785-before .
            $ docker run -i --rm --publish 8080:8080 --publish 50000:50000 --publish 18022:18022 -t jenkins:JENKINS-41785-before
          {code}
          # Open a web browser to that running docker instance
          # Open the "Bugs - Pipeline Checks" folder
          # Observe the icon for the jenkins-bugs multi-branch pipeline folder
          # Open the jenkins-bugs multi-branch pipeline folder and index the branches
          # Wait until at least one of the pipeline jobs completes
          # Navigate to the "Bus - Pipeline Checks" folder and confirm the status is correct

          Steps to see the unexpected (changed) behavior:

          # Clone my docker instance and checkout the JENKINS-41785-after tag
          {code}
            $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-after
            $ cd JENKINS-41785-after
            $ git checkout -b JENKINS-41785-after JENKINS-41785-after
          {code}
          # Build and run the docker instance
          {code}
            $ docker build -t jenkins:JENKINS-41785-after .
            $ docker run -i --rm --publish 8080:8080 --publish 50000:50000 --publish 18022:18022 -t jenkins:JENKINS-41785-after
          {code}
          # Open a web browser to that running docker instance
          # Open the "Bugs - Pipeline Checks" folder
          # Observe the icon for the jenkins-bugs multi-branch pipeline folder is incorrect (shows no status)
            (see !Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail! )
          # Open the jenkins-bugs multi-branch pipeline folder and index the branches
          # Wait until at least one of the pipeline jobs completes
          # Navigate to the "Bus - Pipeline Checks" folder and confirm the status is still incorrect (shows no status)
            See !Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail!

          The parent folder does still show the "worst status" when it is configured (see !parent-folder-shows-correct-aggregate-color.PNG|thumbnail! ). It seems to only be the pipeline folder that is unable to show worst case status. This might be related to JENKINS-40545, since I see a null pointer exception reported when I try to configure that pipeline job in the folder, though the null pointer exception also appears when I configure a folder in a folder.
          markewaite Mark Waite made changes -
          Description The status icon of multi-branch pipeline jobs in a folder could optionally be adjusted to show the status of the worst job in that multi-branch pipeline as the status for that multi-branch pipeline. Recent updates to plugins have changed that behavior so it no longer shows worst status.

          Steps to see the expected behavior (before the change):

          # Clone my docker instance and checkout the JENKINS-41785-before tag
          {code}
            $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-before
            $ cd JENKINS-41785-before
            $ git checkout -b JENKINS-41785-before JENKINS-41785-before
          {code}
          # Build and run the docker instance
          {code}
            $ docker build -t jenkins:JENKINS-41785-before .
            $ docker run -i --rm --publish 8080:8080 --publish 50000:50000 --publish 18022:18022 -t jenkins:JENKINS-41785-before
          {code}
          # Open a web browser to that running docker instance
          # Open the "Bugs - Pipeline Checks" folder
          # Observe the icon for the jenkins-bugs multi-branch pipeline folder
          # Open the jenkins-bugs multi-branch pipeline folder and index the branches
          # Wait until at least one of the pipeline jobs completes
          # Navigate to the "Bus - Pipeline Checks" folder and confirm the status is correct

          Steps to see the unexpected (changed) behavior:

          # Clone my docker instance and checkout the JENKINS-41785-after tag
          {code}
            $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-after
            $ cd JENKINS-41785-after
            $ git checkout -b JENKINS-41785-after JENKINS-41785-after
          {code}
          # Build and run the docker instance
          {code}
            $ docker build -t jenkins:JENKINS-41785-after .
            $ docker run -i --rm --publish 8080:8080 --publish 50000:50000 --publish 18022:18022 -t jenkins:JENKINS-41785-after
          {code}
          # Open a web browser to that running docker instance
          # Open the "Bugs - Pipeline Checks" folder
          # Observe the icon for the jenkins-bugs multi-branch pipeline folder is incorrect (shows no status)
            (see !Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail! )
          # Open the jenkins-bugs multi-branch pipeline folder and index the branches
          # Wait until at least one of the pipeline jobs completes
          # Navigate to the "Bus - Pipeline Checks" folder and confirm the status is still incorrect (shows no status)
            See !Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail!

          The parent folder does still show the "worst status" when it is configured (see !parent-folder-shows-correct-aggregate-color.PNG|thumbnail! ). It seems to only be the pipeline folder that is unable to show worst case status. This might be related to JENKINS-40545, since I see a null pointer exception reported when I try to configure that pipeline job in the folder, though the null pointer exception also appears when I configure a folder in a folder.
          The status icon of multi-branch pipeline jobs in a folder could optionally be adjusted to show the status of the worst job in that multi-branch pipeline as the status for that multi-branch pipeline. Recent updates to plugins have changed that behavior so it no longer shows worst status.

          Steps to see the expected behavior (before the change):

          # Clone my docker instance and checkout the JENKINS-41785-before tag
          {code}
            $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-before
            $ cd JENKINS-41785-before
            $ git checkout -b JENKINS-41785-before JENKINS-41785-before
          {code}
          # Build and run the docker instance
          {code}
            $ docker build -t jenkins:JENKINS-41785-before .
            $ docker run -i --rm --publish 8080:8080 --publish 50000:50000 --publish 18022:18022 -t jenkins:JENKINS-41785-before
          {code}
          # Open a web browser to that running docker instance
          # Open the "Bugs - Pipeline Checks" folder
          # Observe the icon for the jenkins-bugs multi-branch pipeline folder
          # Open the jenkins-bugs multi-branch pipeline folder and index the branches
          # Wait until at least one of the pipeline jobs completes
          # Navigate to the "Bus - Pipeline Checks" folder and confirm the status is correct

          Steps to see the unexpected (changed) behavior:

          # Clone my docker instance and checkout the JENKINS-41785-after tag
          {code}
            $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-after
            $ cd JENKINS-41785-after
            $ git checkout -b JENKINS-41785-after JENKINS-41785-after
          {code}
          # Build and run the docker instance
          {code}
            $ docker build -t jenkins:JENKINS-41785-after .
            $ docker run -i --rm --publish 8080:8080 --publish 50000:50000 --publish 18022:18022 -t jenkins:JENKINS-41785-after
          {code}
          # Open a web browser to that running docker instance
          # Open the "Bugs - Pipeline Checks" folder
          # Observe the icon for the jenkins-bugs multi-branch pipeline folder is incorrect (shows no status)
            !Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail!
          # Open the jenkins-bugs multi-branch pipeline folder and index the branches
          # Wait until at least one of the pipeline jobs completes
          # Navigate to the "Bus - Pipeline Checks" folder and confirm the status is still incorrect (shows no status)
            !Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail!

          The parent folder does still show the "worst status" when it is configured (see !parent-folder-shows-correct-aggregate-color.PNG|thumbnail! ). It seems to only be the pipeline folder that is unable to show worst case status. This might be related to JENKINS-40545, since I see a null pointer exception reported when I try to configure that pipeline job in the folder, though the null pointer exception also appears when I configure a folder in a folder.
          markewaite Mark Waite made changes -
          Summary Multi-branch pipeline status icon no longer shows worst status of jobs in that job Multi-branch pipeline status icon no longer shows worst status of jobs in that multi-branch 'folder'
          recampbell Ryan Campbell made changes -
          Assignee Stephen Connolly [ stephenconnolly ]
          Hide
          recampbell Ryan Campbell added a comment -

          Thanks for the detailed steps to reproduce. Stephen Connolly, I think we need to prioritize this one.

          Show
          recampbell Ryan Campbell added a comment - Thanks for the detailed steps to reproduce. Stephen Connolly , I think we need to prioritize this one.
          Hide
          jadchamoun Jad Chamoun added a comment -

          It's the same here, ever since updating to 2.12. Thank you Mark Waite for reporting it.

          Show
          jadchamoun Jad Chamoun added a comment - It's the same here, ever since updating to 2.12. Thank you Mark Waite for reporting it.
          Hide
          stephenconnolly Stephen Connolly added a comment -

          Patrick Wolf We need to discuss this one. The ability to configure a custom folder icon was only exposed by accident in the original implementation. With 2.0.x this was locked down as the API to lock it down was made available. To support the customization would require adding some sort of organization folder property that allows delegating the configuration to the child projects (as child projects are read-only, so would need configuration at the organization folder level).

          In short, getting a consistent UI for this that works for both raw multi-branch projects and multi-branch projects in an org folder is not a trivial solution, and given that the design is that the avatar be displayed in the status icon rather than an aggregate status, I am inclined to mark this as WONTFIX. On the other hand, I can see the utility for some users in being able to get the aggregate status... WDYT?

          Show
          stephenconnolly Stephen Connolly added a comment - Patrick Wolf We need to discuss this one. The ability to configure a custom folder icon was only exposed by accident in the original implementation. With 2.0.x this was locked down as the API to lock it down was made available. To support the customization would require adding some sort of organization folder property that allows delegating the configuration to the child projects (as child projects are read-only, so would need configuration at the organization folder level). In short, getting a consistent UI for this that works for both raw multi-branch projects and multi-branch projects in an org folder is not a trivial solution, and given that the design is that the avatar be displayed in the status icon rather than an aggregate status, I am inclined to mark this as WONTFIX. On the other hand, I can see the utility for some users in being able to get the aggregate status... WDYT?
          stephenconnolly Stephen Connolly made changes -
          Labels scm-api-tidy-scrub
          jglick Jesse Glick made changes -
          Component/s workflow-multibranch-plugin [ 21465 ]
          Labels scm-api-tidy-scrub multibranch scm-api-tidy-scrub
          stephenconnolly Stephen Connolly made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Not A Defect [ 7 ]
          stephenconnolly Stephen Connolly made changes -
          Status Resolved [ 5 ] Closed [ 6 ]

            People

            • Assignee:
              stephenconnolly Stephen Connolly
              Reporter:
              markewaite Mark Waite
            • Votes:
              4 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: