[JENKINS-12642] Build name only applied to multi-configuration axis

[jenkins-infra-bot]

When using the version number plugin in a multiconfiguration job, the customized build name is only visible in the configuration axis jobs.

Example:

MyJob -- Axis1
      -- Axis2
      -- Axis3

Let's say we use a build name pattern like this: SOMESTRING-${BUILD_NAME}-#${BUILD_NUMBER}
After a succesful build the result will be:

MyJob -- Axis1 (SOMESTRING-MyJob-#1) 
      -- Axis2 (SOMESTRING-MyJob-#1) 
      -- Axis3 (SOMESTRING-MyJob-#1)

The expected behavior would be something like this:

MyJob (SOMESTRING-MyJob-#1) -- Axis1 (SOMESTRING-MyJob-#1) 
    -- Axis2 (SOMESTRING-MyJob-#1) 
    -- Axis3 (SOMESTRING-MyJob-#1)

Steps to reproduce:

• Create a new multiconfiguration job.
• Add some axis.
• In the job configuration, tick the "Create a formatted version number" checkbox.
• Fill any pattern in the "Version Number Format String" box.
• Tick the "Use the formatted version number for build display name." checkbox.
• Start a build.
• The custom build name will only be visible in a specific axis and not on the main job page.

---

Originally reported by cbab, imported from: Build name only applied to multi-configuration axis

• status: Open
• priority: Major
• component(s): versionnumber-plugin
• label(s): plugin
• resolution: Unresolved
• votes: 3
• watchers: 3
• imported: 20251216-225446

Raw content of original issue

When using the version number plugin in a multiconfiguration job, the customized build name is only visible in the configuration axis jobs.

Example:


MyJob -- Axis1
      -- Axis2
      -- Axis3

Let's say we use a build name pattern like this: SOMESTRING-${BUILD_NAME}-#${BUILD_NUMBER}
After a succesful build the result will be:

MyJob -- Axis1 (SOMESTRING-MyJob-#1) 
      -- Axis2 (SOMESTRING-MyJob-#1) 
      -- Axis3 (SOMESTRING-MyJob-#1)

The expected behavior would be something like this:

MyJob (SOMESTRING-MyJob-#1) -- Axis1 (SOMESTRING-MyJob-#1) 
                            -- Axis2 (SOMESTRING-MyJob-#1) 
                            -- Axis3 (SOMESTRING-MyJob-#1)

Steps to reproduce:

	
Create a new multiconfiguration job.
	
Add some axis.
	
In the job configuration, tick the "Create a formatted version number" checkbox.
	
Fill any pattern in the "Version Number Format String" box.
	
Tick the "Use the formatted version number for build display name." checkbox.
	
Start a build.
	
The custom build name will only be visible in a specific axis and not on the main job page.

[jenkins-infra-bot]

wilddeej:

• Original comment link
• Raw content of original comment:

  I have noticed an additional undesirable side-effect from this issue:  if using any of the very-useful BUILDS_TODAY, BUILDS_THIS_WEEK, BUILDS_THIS_MONTH, BUILDS_THIS_YEAR, or (my favorite) BUILDS_ALL_TIME variables, these only apply at the configuration level, not on a global basis.  So there is no guarantee that these will be consistent between the various configurations (jobs) of a given project.  I confirmed this by adding a new axis to an existing multiconfiguration project, and the new axis showed up as #1, rather than #3 as all other axes.
  Unfortunately, this means I can't use this potentially excellent plugin for my purposes;  the axes MUST be consistent with the top-level job (which also needs to show that version number but does not, as Christian Babeux already carefully reports).
  

I have noticed an additional undesirable side-effect from this issue: if using any of the very-useful BUILDS_TODAY, BUILDS_THIS_WEEK, BUILDS_THIS_MONTH, BUILDS_THIS_YEAR, or (my favorite) BUILDS_ALL_TIME variables, these only apply at the configuration level, not on a global basis. So there is no guarantee that these will be consistent between the various configurations (jobs) of a given project. I confirmed this by adding a new axis to an existing multiconfiguration project, and the new axis showed up as #1, rather than #3 as all other axes.
Unfortunately, this means I can't use this potentially excellent plugin for my purposes; the axes MUST be consistent with the top-level job (which also needs to show that version number but does not, as Christian Babeux already carefully reports).