+1

My team also uses currentBuild.description and currentBuild.displayName quite heavily.  It is much more useful to have a version number in the build column than it does a generic number.

Thanks akrapfl - we are considering this one.

Reopened as we can implement JENKINS-41769 pretty quickly but this one requires a bit more effort due to the "Run" column being a bit longer and our tables will need to change.

It will look a bit like this

We may have some troubles on very long display names but that will have to wait until we get our tables updated to the new style. For the moment, we've made it so you can hover to get the full title.

Will be released in Blue Ocean 1.1

I don't think this is working properly now.

We have complex jobs that use displayName heavily. We're explicitly using displayName to be able to quickly look at the list of builds and know which one did what. While the main build screen does show the name in the top of the page, the activity screen does not show it anywhere, not even on mouse hover as mentioned in previous comment on this issue. It just shows the build number.

Here are example jobs that use displayName heavily (These should be publicly viewable):

http://jenkins.ovirt.org/job/ovirt-master_change-queue/

http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/

It is pretty important for us to see the right display names, otherwise we can't use BlueOcean to monitor these jobs.

Please open a new bug with a Jenkinsfile that can reproduce the error, rather than reopen this ticket.

jamesdumay bkorren I see this as still broken as well.  Or rather, partially working:

the following groovy on blue ocean: 1.2.0 · Core 2.60.3 · 4d42c87 · (no branch) 

node {
 stage('start') {
 currentBuild.displayName = "foo.$BUILD_NUMBER"
 currentBuild.description = "foo.$BUILD_NUMBER - desc"
 echo 'Hello World'
 }
}

produces the attached ui in classic and blue ocean views.

jamesdumay bkorren

Added JENKINS-46657 to track the defect with this feature.