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

Jobs triggered with the Downstream-Ext plugin are not displayed by the Downstream BuildView plugin

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • downstream-buildview-plugin
    • None
    • Master on Solaris
      Slaves on Solaris and linux
      Jenkins 1.404

      With an example where :
      Start job triggers in parallel LVL10 and LVL11
      Once finished, via a join, Start Job triggers LVL20 and LVL21, and then, in a post join action LVL3
      The attached screenshot shows that the whole subtree is shown twice. One for each level1 parallel jobs.
      Moreover, if the status is correctly displayed under LVL10, it is not under LVL11.

      So, the display has some bugs and is not really what we could await. Something like :

       
Start
|______
    | |----------LVL10
    | |----------LVL11
    =============
    |------------------------LV20
    |------------------------LV21
        |------------------------LV3

      would have been easiest to read.
      Let's imagine what will happened in complex context with a tenth à parallel jobs at each level, if the complete job cascade at levels n-1 is repeated for each level n paralell jobs !
      See the Downstream Build View with a Post Join screenshot.

        1. Downstream BuildView with a Join and PostJoin.jpg
          Downstream BuildView with a Join and PostJoin.jpg
          91 kB

          [JENKINS-10750] Jobs triggered with the Downstream-Ext plugin are not displayed by the Downstream BuildView plugin

          jlpinardon created issue -
          jlpinardon made changes -
          Attachment New: Downstream BuildView with a Join and PostJoin.jpg [ 20735 ]
          jlpinardon made changes -
          Description Original: With an example where :
          Start job triggers in parallel LVL10 and LVL11
          Once finished, via a join, Start Job triggers LVL20 and LVL21, and then, in a post join action LVL3
          The attached screenshot shows that the whole subtree is shown twice. One for each level1 parallel jobs.
          Moreover, if the status is correctly displayed under LVL10, it is not under LVL11.

          So, the display has some bugs and is not really what we could await. Something like :
          Start
          |______
              | |----------LVL10
              | |----------LVL11
              =============
              |------------------------LV20
              |------------------------LV21
                  |------------------------LV3
          would have been easiest to read.
          Let's imagine what will happened in complex context with a tenth à parallel jobs at each level, if the complete job cascade at levels n-1 is repeated for each level n paralell jobs !
          See the Downstream Build View with a Post Join screenshot.           		New: With an example where :
          Start job triggers in parallel LVL10 and LVL11
          Once finished, via a join, Start Job triggers LVL20 and LVL21, and then, in a post join action LVL3
          The attached screenshot shows that the whole subtree is shown twice. One for each level1 parallel jobs.
          Moreover, if the status is correctly displayed under LVL10, it is not under LVL11.

          So, the display has some bugs and is not really what we could await. Something like :
          {quote}
          {noformat}
          Start
          |______
              | |----------LVL10
              | |----------LVL11
              =============
              |------------------------LV20
              |------------------------LV21
                  |------------------------LV3
          {noformat}
          {quote}
          would have been easiest to read.
          Let's imagine what will happened in complex context with a tenth à parallel jobs at each level, if the complete job cascade at levels n-1 is repeated for each level n paralell jobs !
          See the Downstream Build View with a Post Join screenshot.

          Florian Loikasek added a comment -

          The description discusses the Join plugin. The display suggestion would enhance 8733 in a fine way...

          Florian Loikasek added a comment - The description discusses the Join plugin. The display suggestion would enhance 8733 in a fine way...
          Florian Loikasek made changes -
          Link New: This issue duplicates JENKINS-6365 [ JENKINS-6365 ]
          Florian Loikasek made changes -
          Link New: This issue duplicates JENKINS-8733 [ JENKINS-8733 ]
          Florian Loikasek made changes -
          Link New: This issue duplicates JENKINS-9064 [ JENKINS-9064 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 140952 ] New: JNJira + In-Review [ 175379 ]

            shinodkm shinodkm
            jlpinardon jlpinardon
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: