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

Can only select top node of parallel nodes while job is in progress.

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: blueocean-plugin
    • Labels:
    • Environment:
      Firefox 51.0
      Chrome Version 54.0.2840.99 m (64-bit)
      Microsoft Edge 38.14393.0.0
      Jenkins 2.17
      Blue Ocean 1.0.0-b24
    • Similar Issues:
    • Sprint:
      1.0, Blue Ocean 1.0-rc3, Blue Ocean 1.0-rc4, Blue Ocean - 1.1-beta-1, Blue Ocean - 1.1-beta2

      Description

      During a build I have an init stage followed by a parallel section with 4 stages

      init ---|--Linux Release
              -|--Linux Debug
              -|--Windows Release
              -|--Windows Debug
      

      During the build I try to click on a node in the parallel section other than Linux Release the UI doesn't update (Doesn't have to be Linux Release, it's whatever the topmost node displayed in the parallel section is, I reordered the script to test this)
      But if I click the "init" node (which is already complete and outside the paralell section) it happily updates the UI (I noticed it basically just adds a number to the end of the URL).

      I put some break points into the javascript and found that it's at least getting as far as this bit of code:

              key: 'nodeClicked',
              value: function nodeClicked(node) {
                  var stage = node.stage;
                  var listener = this.props.onNodeClick;
      
                  if (listener) {
                      listener(stage.name, stage.id);
                  }
      
                  // Update selection
                  this.setState({ selectedStage: stage });
      

      When I manually append the stage.id of a node in the parallel section to the URL and refresh the page then the view updates correctly and I can see the status of the node I had clicked on. (I find the node stage.id by clicking the node I want and hitting a breakpoint I set in the above code and then checking the value of the stage.id)

        Attachments

          Issue Links

            Activity

            astoker austin stoker created issue -
            astoker austin stoker made changes -
            Field Original Value New Value
            Description During a build I have an init stage followed by a parallel section with 4 stages
            init --|--Linux Release
                    |--Linux Debug
                    |--Windows Release
                    |--Windows Debug
            during the build I try to click on a node in the parallel section other than Linux Release (or whatever the topmost node displayed in the parallel section is, I reordered the script to test this) the UI doesn't update. But if I click the "init" node (which is already complete and outside the paralell section) it happily updates the UI (I noticed it basically just adds a number to the end of the URL). I put some break points into the javascript and found that it's at least getting as far as this bit of code:
                    key: 'nodeClicked',
                    value: function nodeClicked(node) {
                        var stage = node.stage;
                        var listener = this.props.onNodeClick;

                        if (listener) {
                            listener(stage.name, stage.id);
                        }

                        // Update selection
                        this.setState({ selectedStage: stage });

            If I manually append the stage.id of a node in the parallel section (which I find by clicking the node I want and hitting a breakpoint I set in the above code and then checking the value of the stage.id) to the URL and refresh the page then the view updates correctly and I can see the status of the node I had clicked on.
            During a build I have an init stage followed by a parallel section with 4 stages
            init ---|--Linux Release
                    -|--Linux Debug
                    -|--Windows Release
                    -|--Windows Debug
            during the build I try to click on a node in the parallel section other than Linux Release (or whatever the topmost node displayed in the parallel section is, I reordered the script to test this) the UI doesn't update. But if I click the "init" node (which is already complete and outside the paralell section) it happily updates the UI (I noticed it basically just adds a number to the end of the URL). I put some break points into the javascript and found that it's at least getting as far as this bit of code:
                    key: 'nodeClicked',
                    value: function nodeClicked(node) {
                        var stage = node.stage;
                        var listener = this.props.onNodeClick;

                        if (listener) {
                            listener(stage.name, stage.id);
                        }

                        // Update selection
                        this.setState({ selectedStage: stage });

            If I manually append the stage.id of a node in the parallel section (which I find by clicking the node I want and hitting a breakpoint I set in the above code and then checking the value of the stage.id) to the URL and refresh the page then the view updates correctly and I can see the status of the node I had clicked on.
            astoker austin stoker made changes -
            Description During a build I have an init stage followed by a parallel section with 4 stages
            init ---|--Linux Release
                    -|--Linux Debug
                    -|--Windows Release
                    -|--Windows Debug
            during the build I try to click on a node in the parallel section other than Linux Release (or whatever the topmost node displayed in the parallel section is, I reordered the script to test this) the UI doesn't update. But if I click the "init" node (which is already complete and outside the paralell section) it happily updates the UI (I noticed it basically just adds a number to the end of the URL). I put some break points into the javascript and found that it's at least getting as far as this bit of code:
                    key: 'nodeClicked',
                    value: function nodeClicked(node) {
                        var stage = node.stage;
                        var listener = this.props.onNodeClick;

                        if (listener) {
                            listener(stage.name, stage.id);
                        }

                        // Update selection
                        this.setState({ selectedStage: stage });

            If I manually append the stage.id of a node in the parallel section (which I find by clicking the node I want and hitting a breakpoint I set in the above code and then checking the value of the stage.id) to the URL and refresh the page then the view updates correctly and I can see the status of the node I had clicked on.
            During a build I have an init stage followed by a parallel section with 4 stages
            ```
            init ---|--Linux Release
                    -|--Linux Debug
                    -|--Windows Release
                    -|--Windows Debug
            ```
            during the build I try to click on a node in the parallel section other than Linux Release (or whatever the topmost node displayed in the parallel section is, I reordered the script to test this) the UI doesn't update. But if I click the "init" node (which is already complete and outside the paralell section) it happily updates the UI (I noticed it basically just adds a number to the end of the URL). I put some break points into the javascript and found that it's at least getting as far as this bit of code:
                    key: 'nodeClicked',
                    value: function nodeClicked(node) {
                        var stage = node.stage;
                        var listener = this.props.onNodeClick;

                        if (listener) {
                            listener(stage.name, stage.id);
                        }

                        // Update selection
                        this.setState({ selectedStage: stage });

            If I manually append the stage.id of a node in the parallel section (which I find by clicking the node I want and hitting a breakpoint I set in the above code and then checking the value of the stage.id) to the URL and refresh the page then the view updates correctly and I can see the status of the node I had clicked on.
            astoker austin stoker made changes -
            Description During a build I have an init stage followed by a parallel section with 4 stages
            ```
            init ---|--Linux Release
                    -|--Linux Debug
                    -|--Windows Release
                    -|--Windows Debug
            ```
            during the build I try to click on a node in the parallel section other than Linux Release (or whatever the topmost node displayed in the parallel section is, I reordered the script to test this) the UI doesn't update. But if I click the "init" node (which is already complete and outside the paralell section) it happily updates the UI (I noticed it basically just adds a number to the end of the URL). I put some break points into the javascript and found that it's at least getting as far as this bit of code:
                    key: 'nodeClicked',
                    value: function nodeClicked(node) {
                        var stage = node.stage;
                        var listener = this.props.onNodeClick;

                        if (listener) {
                            listener(stage.name, stage.id);
                        }

                        // Update selection
                        this.setState({ selectedStage: stage });

            If I manually append the stage.id of a node in the parallel section (which I find by clicking the node I want and hitting a breakpoint I set in the above code and then checking the value of the stage.id) to the URL and refresh the page then the view updates correctly and I can see the status of the node I had clicked on.
            During a build I have an init stage followed by a parallel section with 4 stages
            init ---|--Linux Release
                    -|--Linux Debug
                    -|--Windows Release
                    -|--Windows Debug
            during the build I try to click on a node in the parallel section other than Linux Release (or whatever the topmost node displayed in the parallel section is, I reordered the script to test this) the UI doesn't update. But if I click the "init" node (which is already complete and outside the paralell section) it happily updates the UI (I noticed it basically just adds a number to the end of the URL). I put some break points into the javascript and found that it's at least getting as far as this bit of code:
                    key: 'nodeClicked',
                    value: function nodeClicked(node) {
                        var stage = node.stage;
                        var listener = this.props.onNodeClick;

                        if (listener) {
                            listener(stage.name, stage.id);
                        }

                        // Update selection
                        this.setState({ selectedStage: stage });

            If I manually append the stage.id of a node in the parallel section (which I find by clicking the node I want and hitting a breakpoint I set in the above code and then checking the value of the stage.id) to the URL and refresh the page then the view updates correctly and I can see the status of the node I had clicked on.
            astoker austin stoker made changes -
            Description During a build I have an init stage followed by a parallel section with 4 stages
            init ---|--Linux Release
                    -|--Linux Debug
                    -|--Windows Release
                    -|--Windows Debug
            during the build I try to click on a node in the parallel section other than Linux Release (or whatever the topmost node displayed in the parallel section is, I reordered the script to test this) the UI doesn't update. But if I click the "init" node (which is already complete and outside the paralell section) it happily updates the UI (I noticed it basically just adds a number to the end of the URL). I put some break points into the javascript and found that it's at least getting as far as this bit of code:
                    key: 'nodeClicked',
                    value: function nodeClicked(node) {
                        var stage = node.stage;
                        var listener = this.props.onNodeClick;

                        if (listener) {
                            listener(stage.name, stage.id);
                        }

                        // Update selection
                        this.setState({ selectedStage: stage });

            If I manually append the stage.id of a node in the parallel section (which I find by clicking the node I want and hitting a breakpoint I set in the above code and then checking the value of the stage.id) to the URL and refresh the page then the view updates correctly and I can see the status of the node I had clicked on.
            During a build I have an init stage followed by a parallel section with 4 stages
            {noformat}
            init ---|--Linux Release
                    -|--Linux Debug
                    -|--Windows Release
                    -|--Windows Debug
            during the build I try to click on a node in the parallel section other than Linux Release (or whatever the topmost node displayed in the parallel section is, I reordered the script to test this) the UI doesn't update. But if I click the "init" node (which is already complete and outside the paralell section) it happily updates the UI (I noticed it basically just adds a number to the end of the URL). I put some break points into the javascript and found that it's at least getting as far as this bit of code:
                    key: 'nodeClicked',
                    value: function nodeClicked(node) {
                        var stage = node.stage;
                        var listener = this.props.onNodeClick;

                        if (listener) {
                            listener(stage.name, stage.id);
                        }

                        // Update selection
                        this.setState({ selectedStage: stage });

            If I manually append the stage.id of a node in the parallel section (which I find by clicking the node I want and hitting a breakpoint I set in the above code and then checking the value of the stage.id) to the URL and refresh the page then the view updates correctly and I can see the status of the node I had clicked on.
            astoker austin stoker made changes -
            Description During a build I have an init stage followed by a parallel section with 4 stages
            {noformat}
            init ---|--Linux Release
                    -|--Linux Debug
                    -|--Windows Release
                    -|--Windows Debug
            during the build I try to click on a node in the parallel section other than Linux Release (or whatever the topmost node displayed in the parallel section is, I reordered the script to test this) the UI doesn't update. But if I click the "init" node (which is already complete and outside the paralell section) it happily updates the UI (I noticed it basically just adds a number to the end of the URL). I put some break points into the javascript and found that it's at least getting as far as this bit of code:
                    key: 'nodeClicked',
                    value: function nodeClicked(node) {
                        var stage = node.stage;
                        var listener = this.props.onNodeClick;

                        if (listener) {
                            listener(stage.name, stage.id);
                        }

                        // Update selection
                        this.setState({ selectedStage: stage });

            If I manually append the stage.id of a node in the parallel section (which I find by clicking the node I want and hitting a breakpoint I set in the above code and then checking the value of the stage.id) to the URL and refresh the page then the view updates correctly and I can see the status of the node I had clicked on.
            During a build I have an init stage followed by a parallel section with 4 stages
            {noformat}
            init ---|--Linux Release
                    -|--Linux Debug
                    -|--Windows Release
                    -|--Windows Debug
            {noformat}
            during the build I try to click on a node in the parallel section other than Linux Release (or whatever the topmost node displayed in the parallel section is, I reordered the script to test this) the UI doesn't update. But if I click the "init" node (which is already complete and outside the paralell section) it happily updates the UI (I noticed it basically just adds a number to the end of the URL). I put some break points into the javascript and found that it's at least getting as far as this bit of code:
                    key: 'nodeClicked',
                    value: function nodeClicked(node) {
                        var stage = node.stage;
                        var listener = this.props.onNodeClick;

                        if (listener) {
                            listener(stage.name, stage.id);
                        }

                        // Update selection
                        this.setState({ selectedStage: stage });

            If I manually append the stage.id of a node in the parallel section (which I find by clicking the node I want and hitting a breakpoint I set in the above code and then checking the value of the stage.id) to the URL and refresh the page then the view updates correctly and I can see the status of the node I had clicked on.
            astoker austin stoker made changes -
            Description During a build I have an init stage followed by a parallel section with 4 stages
            {noformat}
            init ---|--Linux Release
                    -|--Linux Debug
                    -|--Windows Release
                    -|--Windows Debug
            {noformat}
            during the build I try to click on a node in the parallel section other than Linux Release (or whatever the topmost node displayed in the parallel section is, I reordered the script to test this) the UI doesn't update. But if I click the "init" node (which is already complete and outside the paralell section) it happily updates the UI (I noticed it basically just adds a number to the end of the URL). I put some break points into the javascript and found that it's at least getting as far as this bit of code:
                    key: 'nodeClicked',
                    value: function nodeClicked(node) {
                        var stage = node.stage;
                        var listener = this.props.onNodeClick;

                        if (listener) {
                            listener(stage.name, stage.id);
                        }

                        // Update selection
                        this.setState({ selectedStage: stage });

            If I manually append the stage.id of a node in the parallel section (which I find by clicking the node I want and hitting a breakpoint I set in the above code and then checking the value of the stage.id) to the URL and refresh the page then the view updates correctly and I can see the status of the node I had clicked on.
            During a build I have an init stage followed by a parallel section with 4 stages
            {noformat}
            init ---|--Linux Release
                    -|--Linux Debug
                    -|--Windows Release
                    -|--Windows Debug
            {noformat}
            During the build I try to click on a node in the parallel section other than Linux Release the UI doesn't update (Doesn't have to be Linux Release, it's whatever the topmost node displayed in the parallel section is, I reordered the script to test this)
            But if I click the "init" node (which is already complete and outside the paralell section) it happily updates the UI (I noticed it basically just adds a number to the end of the URL).

            I put some break points into the javascript and found that it's at least getting as far as this bit of code:
            {code:javascript}
                    key: 'nodeClicked',
                    value: function nodeClicked(node) {
                        var stage = node.stage;
                        var listener = this.props.onNodeClick;

                        if (listener) {
                            listener(stage.name, stage.id);
                        }

                        // Update selection
                        this.setState({ selectedStage: stage });
            {code:javascript}

            When I manually append the stage.id of a node in the parallel section to the URL and refresh the page then the view updates correctly and I can see the status of the node I had clicked on. (I find the node stage.id by clicking the node I want and hitting a breakpoint I set in the above code and then checking the value of the stage.id)
            astoker austin stoker made changes -
            Description During a build I have an init stage followed by a parallel section with 4 stages
            {noformat}
            init ---|--Linux Release
                    -|--Linux Debug
                    -|--Windows Release
                    -|--Windows Debug
            {noformat}
            During the build I try to click on a node in the parallel section other than Linux Release the UI doesn't update (Doesn't have to be Linux Release, it's whatever the topmost node displayed in the parallel section is, I reordered the script to test this)
            But if I click the "init" node (which is already complete and outside the paralell section) it happily updates the UI (I noticed it basically just adds a number to the end of the URL).

            I put some break points into the javascript and found that it's at least getting as far as this bit of code:
            {code:javascript}
                    key: 'nodeClicked',
                    value: function nodeClicked(node) {
                        var stage = node.stage;
                        var listener = this.props.onNodeClick;

                        if (listener) {
                            listener(stage.name, stage.id);
                        }

                        // Update selection
                        this.setState({ selectedStage: stage });
            {code:javascript}

            When I manually append the stage.id of a node in the parallel section to the URL and refresh the page then the view updates correctly and I can see the status of the node I had clicked on. (I find the node stage.id by clicking the node I want and hitting a breakpoint I set in the above code and then checking the value of the stage.id)
            During a build I have an init stage followed by a parallel section with 4 stages
            {noformat}
            init ---|--Linux Release
                    -|--Linux Debug
                    -|--Windows Release
                    -|--Windows Debug
            {noformat}
            During the build I try to click on a node in the parallel section other than Linux Release the UI doesn't update (Doesn't have to be Linux Release, it's whatever the topmost node displayed in the parallel section is, I reordered the script to test this)
            But if I click the "init" node (which is already complete and outside the paralell section) it happily updates the UI (I noticed it basically just adds a number to the end of the URL).

            I put some break points into the javascript and found that it's at least getting as far as this bit of code:
            {code:javascript}
                    key: 'nodeClicked',
                    value: function nodeClicked(node) {
                        var stage = node.stage;
                        var listener = this.props.onNodeClick;

                        if (listener) {
                            listener(stage.name, stage.id);
                        }

                        // Update selection
                        this.setState({ selectedStage: stage });
            {code}

            When I manually append the stage.id of a node in the parallel section to the URL and refresh the page then the view updates correctly and I can see the status of the node I had clicked on. (I find the node stage.id by clicking the node I want and hitting a breakpoint I set in the above code and then checking the value of the stage.id)
            jamesdumay James Dumay made changes -
            Assignee Thorsten Scherler [ tscherler ]
            jamesdumay James Dumay made changes -
            Sprint 1.0 [ 221 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Epic Link JENKINS-35750 [ 171713 ]
            jamesdumay James Dumay made changes -
            Priority Major [ 3 ] Minor [ 4 ]
            michaelneale Michael Neale made changes -
            Labels UI UI karaoke
            michaelneale Michael Neale made changes -
            Priority Minor [ 4 ] Major [ 3 ]
            jamesdumay James Dumay made changes -
            Sprint 1.0 [ 221 ] 1.0, 1.0-rc1 [ 221, 261 ]
            tscherler Thorsten Scherler made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            jamesdumay James Dumay made changes -
            Sprint 1.0, Blue Ocean 1.0-rc3 [ 221, 261 ] 1.0, Blue Ocean 1.0-rc3, Blue Ocean 1.0-rc4 [ 221, 261, 281 ]
            tscherler Thorsten Scherler made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            jamesdumay James Dumay made changes -
            Link This issue blocks JENKINS-43270 [ JENKINS-43270 ]
            jamesdumay James Dumay made changes -
            Sprint 1.0, Blue Ocean 1.0-rc3, Blue Ocean 1.0-rc4 [ 221, 261, 281 ] 1.0, Blue Ocean 1.0-rc3, Blue Ocean 1.0-rc4, Blue Ocean - techdebt sprint 1 [ 221, 261, 281, 291 ]
            michaelneale Michael Neale made changes -
            Sprint 1.0, Blue Ocean 1.0-rc3, Blue Ocean 1.0-rc4, Blue Ocean - 1.1-beta-1 [ 221, 261, 281, 291 ] 1.0, Blue Ocean 1.0-rc3, Blue Ocean 1.0-rc4, Blue Ocean - 1.1-beta-1, Blue Ocean - 1.1-beta2 [ 221, 261, 281, 291, 306 ]
            jamesdumay James Dumay made changes -
            Status In Review [ 10005 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            jbriden Jenn Briden made changes -
            Status Resolved [ 5 ] Closed [ 6 ]

              People

              • Assignee:
                tscherler Thorsten Scherler
                Reporter:
                astoker austin stoker
              • Votes:
                1 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: