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

Build History by Node doesn't work with Pipeline

      Browse to <jenkinsServer>/computer/<nodeName>/builds to see build history. For pipeline this page seems disabled. This is understandable because a single pipeline might span multiple nodes so showing a simple pass/fail list of pipeline jobs for a node might not make sense. However this has made it hard to tell at a glance when a certain node is failing more often than other nodes.

      I would like to see the build history page for nodes display the pipeline job name and build number and then maybe the stage name and step number or something that is definitely unique to that node. That way we could quickly browse history at the node level to determine if a particular node has problems.

          [JENKINS-38877] Build History by Node doesn't work with Pipeline

          Nick added a comment - - edited

          Is it possible to trigger a clone freestyle job after the pipeline job completes and pass or fail it based on the pipeline job results? The result wouldn't have accurate info for time or etc but it would quickly show pass / fail results per node and the console output of the freestyle job would link to the pipeline output. I know how to trigger the freestyle clone but I'm not sure if its possible to make it pass or fail based on the pipeline job results.

          Update, it is possible to do this with the Node and Label parameter plugin. Needing the duplicate Freestyle job is a bit of a bummer though

          Nick added a comment - - edited Is it possible to trigger a clone freestyle job after the pipeline job completes and pass or fail it based on the pipeline job results? The result wouldn't have accurate info for time or etc but it would quickly show pass / fail results per node and the console output of the freestyle job would link to the pipeline output. I know how to trigger the freestyle clone but I'm not sure if its possible to make it pass or fail based on the pipeline job results. Update, it is possible to do this with the  Node and Label parameter plugin . Needing the duplicate Freestyle job is a bit of a bummer though

          Is there any chance of reopening this ticket and reconsidering the outcome? Not implementing it leaves setups primarily focused on using pipelines with no usable history of builds and gives no easy way of analyzing what was happening on connected nodes at certain point of time.

          Michał Machnicki added a comment - Is there any chance of reopening this ticket and reconsidering the outcome? Not implementing it leaves setups primarily focused on using pipelines with no usable history of builds and gives no easy way of analyzing what was happening on connected nodes at certain point of time.

          Tim Brown added a comment -

          > Is there any chance of reopening this ticket and reconsidering the outcome?
          +1

          Tim Brown added a comment - > Is there any chance of reopening this ticket and reconsidering the outcome? +1

          Adir added a comment -

          Supports issue re-opening as well. Very useful ability which gone for pipelines users (almost everyone).

          +1

          Adir added a comment - Supports issue re-opening as well. Very useful ability which gone for pipelines users (almost everyone). +1

          john added a comment -

          Likewise, as a heavy pipeline user (aren't we all ?), the Node History page is currently useless.
          +1

          john added a comment - Likewise, as a heavy pipeline user (aren't we all ?), the Node History page is currently useless. +1

          Rasmus added a comment -

          +1

          Rasmus added a comment - +1

          Darsh added a comment -

          +1

          Darsh added a comment - +1

          Dennis added a comment -

          This issue has been "resolved" since no action will be taken. Regardless of how crucial it undoubtedly is. Our group has developed a workable, albeit labor-intensive, approach. Mr. Glick has good reason to recommend reducing your use of Jenkins.

          coreball

           

          Dennis added a comment - This issue has been "resolved" since no action will be taken. Regardless of how crucial it undoubtedly is. Our group has developed a workable, albeit labor-intensive, approach. Mr. Glick has good reason to recommend reducing your use of Jenkins. coreball  

          Heiko Nardmann added a comment - - edited

          Maybe you can collect the basic information by running sth. asynchronously and populate some database with the results? I.e. looking for some '<node>' nodes inside the XML files inside the 'workflow' folder for a build?

           

          Heiko Nardmann added a comment - - edited Maybe you can collect the basic information by running sth. asynchronously and populate some database with the results? I.e. looking for some '<node>' nodes inside the XML files inside the 'workflow' folder for a build?  

          Anton added a comment -

          +1

          As an alternative I can think of using ELK for build analytics.

          Anton added a comment - +1 As an alternative I can think of using ELK for build analytics.

            Unassigned Unassigned
            rainwaj Justin Rainwater
            Votes:
            2 Vote for this issue
            Watchers:
            41 Start watching this issue

              Created:
              Updated:
              Resolved: