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

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • blueocean-plugin
    • 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
    • 1.0, Blue Ocean 1.0-rc3, Blue Ocean 1.0-rc4, Blue Ocean - 1.1-beta-1, Blue Ocean - 1.1-beta2

      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)

          [JENKINS-42312] Can only select top node of parallel nodes while job is in progress.

          austin stoker created issue -
          austin stoker made changes -
          Description Original: 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.           		New: 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.
          austin stoker made changes -
          Description Original: 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.           		New: 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.
          austin stoker made changes -
          Description Original: 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.           		New: 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.
          austin stoker made changes -
          Description Original: 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.           		New: 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.
          austin stoker made changes -
          Description Original: 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.           		New: 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.
          austin stoker made changes -
          Description Original: 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.           		New: 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)
          austin stoker made changes -
          Description Original: 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)           		New: 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)
          James Dumay made changes -
          Assignee New: Thorsten Scherler [ tscherler ]
          James Dumay made changes -
          Sprint New: 1.0 [ 221 ]
          James Dumay made changes -
          Rank New: Ranked higher

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

              Created:
              Updated:
              Resolved: