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

[justinrainwater78@gmail.com (JIRA)]

Justin Rainwater created an issue

Jenkins / JENKINS-38877 Build History by Node doesn't work with Pipeline Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2016/Oct/10 11:36 PM Priority: Major Reporter: Justin Rainwater 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. Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[jglick@cloudbees.com (JIRA)]

Jesse Glick resolved as Won't Do

The way the build history page is implemented is not compatible with Pipeline. This page should not be used anyway—the design is fundamentally unsound in terms of performance (you can easily bring a large installation to its knees by browsing this page). There are various longer-term plans for analytic capabilities.

Jenkins / JENKINS-38877 Build History by Node doesn't work with Pipeline

Change By: Jesse Glick Status: Open Resolved Resolution: Won't Do

Add Comment

[joerg.schwaerzler@infineon.com (JIRA)]

Joerg Schwaerzler commented on JENKINS-38877

Re: Build History by Node doesn't work with Pipeline Thanks for the information. Could you provide a link here to some ticket which I could use to track the progress on the planned analytic capabilities? Thanks.

Add Comment

[jglick@cloudbees.com (JIRA)]

Jesse Glick commented on JENKINS-38877

Re: Build History by Node doesn't work with Pipeline

No such ticket.

Add Comment

[justinrainwater78@gmail.com (JIRA)]

Justin Rainwater commented on JENKINS-38877

Re: Build History by Node doesn't work with Pipeline

So in other words the "various longer-term plans for analytic capabilities" are in no way ready to be shared with users? I will most certainly not be holding my breath. Could you point me towards the documentation where it says the build history page should not be used anyway?

Add Comment

[justinrainwater78@gmail.com (JIRA)]

Justin Rainwater updated an issue

Jenkins / JENKINS-38877

Build History by Node doesn't work with Pipeline

Change By: Justin Rainwater Comment:

So in other words the "various longer-term plans for analytic capabilities" are in no way ready to be shared with users? I will most certainly not be holding my breath. Could you point me towards the documentation where it says the build history page should not be used anyway?

Add Comment

[hkdennis2k@gmail.com (JIRA)]

Dennis Cheung commented on JENKINS-38877

Re: Build History by Node doesn't work with Pipeline Is there a commanded way to check if concurrent running jobs on same node cause some problems/regression? In the old freestyle job, there are records on the history page. It is easy to identify overlapping and blame it for performance regression. However, same information lost and quite hidden from the Pipeline. You cannot even tell which nodes were used without look into the full log.

Add Comment

[justinrainwater78@gmail.com (JIRA)]

Justin Rainwater commented on JENKINS-38877

Re: Build History by Node doesn't work with Pipeline

I agree that it's quite frustrating. It used to be you could at a glance see if a particular node was to blame for repeatedly failing jobs, but now with that information so buried it's not so easy. It seems we have to take matters into our own hands. One approach I'm looking into is to write the node name to currentBuild.description so at least when looking at the build history by job you can see the different nodes that ran each build. Better than nothing.

Add Comment

[joerg.schwaerzler@infineon.com (JIRA)]

Joerg Schwaerzler commented on JENKINS-38877

Re: Build History by Node doesn't work with Pipeline

@Build history by job: Actually what we did is setting the build's display name. Doing that you even see the overview of used nodes in the stage view plugin. As a plus you can use the build filter provided by Jenkins to search for all builds which ran on a specific node. Works quite nice - but unfortunately no replacement for the node's build history.

Add Comment

[justinrainwater78@gmail.com (JIRA)]

Justin Rainwater commented on JENKINS-38877

Re: Build History by Node doesn't work with Pipeline

@Joerg just so I understand correctly, are you saying "build display name" like using the name setter plugin? https://wiki.jenkins-ci.org/display/JENKINS/Build+Name+Setter+Plugin Would you mind pasting in an example of what that end result name looks like? Since our pipeline jobs may run on 4-6 different nodes I can imagine having all of that information in a single build name getting a little unwieldy. Thanks, Justin

Add Comment

[jglick@cloudbees.com (JIRA)]

Jesse Glick commented on JENKINS-38877

Re: Build History by Node doesn't work with Pipeline

You cannot even tell which nodes were used without look into the full log. This is already filed separately: JENKINS-26138

Add Comment

[joerg.schwaerzler@infineon.com (JIRA)]

Joerg Schwaerzler commented on JENKINS-38877

Re: Build History by Node doesn't work with Pipeline

Justin Rainwater: For more than one node per job run this most probably will look messed up. Unfortunately I cannot paste any screenshots here because of security issues - and because I cannot setup a demonstrator instance using more than a single build agent. However setting the build display name is quite straight forward. You may give it a try like: currentBuild.setDisplayName(currentBuild.getDisplayName() + " (${agentName})") Afaik you won't need the build name setter plugin as it's using the currentBuild object.

Add Comment

[damien@addepar.com (JIRA)]

Damien Jiang commented on JENKINS-38877

Re: Build History by Node doesn't work with Pipeline

It's been over a year since  There are various longer-term plans for analytic capabilities. Are there any updates on this? There are two annoyance with pipeline builds on multiple nodes: 1. It's hard to tell which nodes were used for which pipeline steps (addressed by the "setting build display name" idea in the comments here) 2. It's hard to tell which jobs/pipeline steps were run on a node, which is what this ticket was originally about.   Are there any workarounds for the latter?

Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[DTaylorBusiness@gmail.com (JIRA)]

David Taylor commented on JENKINS-38877

Re: Build History by Node doesn't work with Pipeline

Why is this marked as Resolved? The original request was to be able to see build history of pipelines under each node's "Build History" section. Its May 2018 and pipelines still do not show up in this section. This ticket should not be marked as Resolved.

Add Comment

[jglick@cloudbees.com (JIRA)]

Jesse Glick commented on JENKINS-38877

Re: Build History by Node doesn't work with Pipeline

Resolved as “will not do”, which stands.

Add Comment

[noamangel@gmail.com (JIRA)]

Noam Angel commented on JENKINS-38877

Re: Build History by Node doesn't work with Pipeline

any workaround for this?

Add Comment

[justinrainwater78@gmail.com (JIRA)]

Justin Rainwater commented on JENKINS-38877

Re: Build History by Node doesn't work with Pipeline

We have built our own solution. Post build results to a database or google sheet and view history by node there. CloudBees has no plans to take care of this so we have to take matters into our own hands.

Add Comment

[wizofaus@hotmail.com (JIRA)]

Dylan Nicholson commented on JENKINS-38877

Re: Build History by Node doesn't work with Pipeline

Agreed, this is an essential feature.  This shouldn't be marked as "Resolved" at all.

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[wizofaus@hotmail.com (JIRA)]

Dylan Nicholson edited a comment on JENKINS-38877

Re: Build History by Node doesn't work with Pipeline

Agreed, this is an essential feature.  This shouldn't be marked as "Resolved" at all.  And it makes perfect sense to be able to see the pipeline stages that ran on each node as jobs, especially with any info about whether they failed.

Add Comment

[justinrainwater78@gmail.com (JIRA)]

Justin Rainwater commented on JENKINS-38877

Re: Build History by Node doesn't work with Pipeline

It's "resolved" because they're not gonna do anything about it. Regardless of how essential it may be. Our team has rolled our own solution which gets the job done despite requiring a ton of work. There's a reason Mr. Glick is suggesting everyone use Jenkins less. https://www.youtube.com/watch?v=Zeqc6--0eQw

Add Comment

[alex.dover@gmail.com (JIRA)]

Alex Dover commented on JENKINS-38877

Re: Build History by Node doesn't work with Pipeline

Essential feature with no alternatives. Can;t believe it's just abandoned

Add Comment

[alex.dover@gmail.com (JIRA)]

Alex Dover edited a comment on JENKINS-38877

Re: Build History by Node doesn't work with Pipeline

Essential feature with no alternatives. Can ; ' t believe it's just abandoned :(

Add Comment

[oxygenxo@gmail.com (JIRA)]

Andrey Babushkin commented on JENKINS-38877

Re: Build History by Node doesn't work with Pipeline

Jesse Glick, are there any alternative ways to find out what builds were scheduled on a node?

Add Comment

[jglick@cloudbees.com (JIRA)]

Jesse Glick commented on JENKINS-38877

Re: Build History by Node doesn't work with Pipeline

Not currently, no.

Add Comment

[aloria@haworthmedia.com (JIRA)]

Angelo Loria commented on JENKINS-38877

Re: Build History by Node doesn't work with Pipeline

Having this feature would be great.

Add Comment

[dan.dragomirescu@bytex.ro (JIRA)]

Dan Dragomirescu commented on JENKINS-38877

Re: Build History by Node doesn't work with Pipeline

Justin Rainwater Hello. Since this hasn't been resolved, do you mind sharing the basic concept of how you got the job done? I'd really, really could use some help on this... Jesse Glick are you aware of any workarounds?

Add Comment

[jglick@cloudbees.com (JIRA)]

Jesse Glick commented on JENKINS-38877

Re: Build History by Node doesn't work with Pipeline

Well, it would be a few lines of Groovy scripting to calculate this…but as mentioned above, if you have a lot of historical builds, the performance will be abysmal (especially on HDDs) since an unbounded number of little XML files would need to be loaded from disk and deserialized into memory, then discarded shortly afterward once the system gets into a low memory condition. That is true of freestyle builds and would be worse still for Pipeline builds due to the more complex metadata. A supportable solution would need something like a database that gets updated when a build uses a node—not a difficult programming project at all, but logistically a problem since Jenkins currently lacks any kind of standardized database, so you would need to either initiate that effort, or do a one-off hack with some sort of text file stored in a node’s configuration directory.

Add Comment