Complementary to JENKINS-46657 allowing currentBuild.displayName, where the RUN column is no longer simply #1-1000, this now needs to accommodate typical build/release names, which potentially may be prefixed by target environment and/or dynamic job status.

In our system, using the MESSAGE column description as an "alternative" is inadequate, as this shows "Started by <user>/upstream job" or "Replayed #?".

So, the expectation is that RUN column shows the full currentBuild.displayName buildName, whatever width it needs to be.

Thanks for your attention to this detail.

does anybody have a solution yet? I'd like to see the RUN column to take up more space (1.5x or 2x)

Michael Neale Sorry for the confusion. I referred to Gavin Mogan's comment and JENKINS-46521

Mock up:

• Now/old:
• Future/new:

Reinhold Füreder having trouble following - any chance you can mock it up what it may look like in your case? 

Oh yes, this sounds like a great idea:

• hiding the "Commit" column for a non-multi branch pipeline in favour of showing the full build display number in the BO's activity tab "Run" id column (see JENKINS-44869) would be ideal/fine for me
  • because I have the commit ID (SVN revision or shortened GIT commit hash) as suffix of my therefore quite long build display number, e.g. "20170613-161100-rev134098" (i.e. "<date>-<time>-rev<SVN revision>")