-
Bug
-
Resolution: Won't Do
-
Major
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.
- is duplicated by
-
-
- Resolved
-
- relates to
-
JENKINS-59409 Please support logging stages that are tasked to a node
-
- Open
-
-
-
- Closed
-
[JENKINS-38877] Build History by Node doesn't work with Pipeline
Justin Rainwater
created issue -
| Resolution | New: Won't Do [ 10001 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
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.
Justin Rainwater
made changes -
| 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? ] |
Dennis Cheung
added a comment - 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.
Dennis Cheung
added a comment - 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. Justin Rainwater
added a comment - 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.
Justin Rainwater
added a comment - 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. @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.
Justin Rainwater
added a comment - @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
Justin Rainwater
added a comment - @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
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.