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

Blue Ocean does not show information about locks and nodes

    • Icon: New Feature New Feature
    • Resolution: Duplicate
    • Icon: Minor Minor
    • blueocean-plugin
    • None

      As a user, I would like all the information which is available in the build log of the Classic Jenkins UI to be available in the Blue Ocean UI.

      Currently the information about acquiring and waiting for locks and nodes is not available in Blue Ocean. I would like to see:

      • That the pipeline is waiting for a node executor or lock.
      • Which node executor or lock the pipeline is waiting for.
      • Which node executor or lock the pipeline successfully acquired.

      The tricky part is to decide how to add this to the Blue Ocean UI.

      Semantically speaking one or more steps / stages are executed in the context of a node and/or lock. Because of that it would make sense to visualize this relation in the UI.

      A possible solution could be to visualize the nodes and lock above or below the pipeline, and have (dotted) lines indicating in which part of the pipeline they are used.

       

       

       

          [JENKINS-44274] Blue Ocean does not show information about locks and nodes

          James Dumay added a comment -

          markl_lagendijk we improved this so that you can see the cause of blockage message as part of JENKINS-41540. There is a Blue Ocean 1.1.0-beta4 release in the experimental update center you can try that should give you this info.

          Would you mind giving it a shot and seeing if it works for you?

          James Dumay added a comment - markl_lagendijk we improved this so that you can see the cause of blockage message as part of JENKINS-41540 . There is a Blue Ocean 1.1.0-beta4 release in the experimental update center you can try that should give you this info. Would you mind giving it a shot and seeing if it works for you?

          jamesdumay nice! This solves the first two points of the issue and with that the UX problem.

          The third point of the issue and the description go into a feature which could be a nice to have.

          Do you think it would be nice if locks and node usage (not just 'waiting for', but also the 'this node/lock is used for these stages')  would be visualized as part of the pipeline view? Or do you think that kind of information is too 'low level' and not interesting to the user?

           

          Mark Lagendijk added a comment - jamesdumay nice! This solves the first two points of the issue and with that the UX problem. The third point of the issue and the description go into a feature which could be a nice to have. Do you think it would be nice if locks and node usage (not just 'waiting for', but also the 'this node/lock is used for these stages')  would be visualized as part of the pipeline view? Or do you think that kind of information is too 'low level' and not interesting to the user?  

          James Dumay added a comment -

          markl_lagendijk certainly we want to improve the experience for Milestone and Lock. We've been tracking this as part of JENKINS-40871. Can you watch that ticket for updates instead of this one? (I will mark this as a duplicate for the time being).

          Take a read of the ticket and add any comments you think would be important for us to consider when we pick this up.

          James Dumay added a comment - markl_lagendijk certainly we want to improve the experience for Milestone and Lock. We've been tracking this as part of JENKINS-40871 . Can you watch that ticket for updates instead of this one? (I will mark this as a duplicate for the time being). Take a read of the ticket and add any comments you think would be important for us to consider when we pick this up.

          jamesdumay First of all sorry for my extremely late response to this for a long time resolved issue. When finding and reading this issue I expected that Blue Ocean (I am using v1.5) already visualizes blockage due to lock (from lockable resources plugin), but I claim it is NOT. The pipeline view showed the previous step at the bottom:

          • where as in classic UI:
            • [Pipeline] sh
              15:40:20 [ACME-Pipeline-WS] Running shell script
              15:40:20 + docker inspect -f . acme/phpstorm:6
              15:40:20 .
              [Pipeline] withDockerContainer
              15:40:20 Jenkins does not seem to be running inside a container
              15:40:20 $ docker run -t -d -u [...] acme/phpstorm:6 cat
              15:40:21 $ docker top 26d9173df385c00d2eeddd5dfd410c332ec7573dfec4166fe439ac1d65e2eb79 -eo pid,comm
              [Pipeline] {
              [Pipeline] lock
              15:40:21 Trying to acquire lock on [Label: PhpStorm, Quantity: 1]
              15:40:21 Found 0 available resource(s). Waiting for correct amount: 1.
              15:40:21 [Label: PhpStorm, Quantity: 1] is locked, waiting...
              

          Please note that the pipeline code from library is more or less (nonetheless I assume/hope this is irrelevant):

              script.docker.image(config.dockerImage).inside(DockerUtil.makePhpStormContainerStartArgs()) { c ->
                script.lock(label: 'PhpStorm', quantity: 1) {
                   ...
          

          Reinhold Füreder added a comment - jamesdumay First of all sorry for my extremely late response to this for a long time resolved issue. When finding and reading this issue I expected that Blue Ocean (I am using v1.5) already visualizes blockage due to lock (from lockable resources plugin), but I claim it is NOT. The pipeline view showed the previous step at the bottom: where as in classic UI: [Pipeline] sh 15:40:20 [ACME-Pipeline-WS] Running shell script 15:40:20 + docker inspect -f . acme/phpstorm:6 15:40:20 . [Pipeline] withDockerContainer 15:40:20 Jenkins does not seem to be running inside a container 15:40:20 $ docker run -t -d -u [...] acme/phpstorm:6 cat 15:40:21 $ docker top 26d9173df385c00d2eeddd5dfd410c332ec7573dfec4166fe439ac1d65e2eb79 -eo pid,comm [Pipeline] { [Pipeline] lock 15:40:21 Trying to acquire lock on [Label: PhpStorm, Quantity: 1] 15:40:21 Found 0 available resource(s). Waiting for correct amount: 1. 15:40:21 [Label: PhpStorm, Quantity: 1] is locked, waiting... Please note that the pipeline code from library is more or less (nonetheless I assume/hope this is irrelevant): script.docker.image(config.dockerImage).inside(DockerUtil.makePhpStormContainerStartArgs()) { c -> script.lock(label: 'PhpStorm' , quantity: 1) { ...

            Unassigned Unassigned
            markl_lagendijk Mark Lagendijk
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: