[JENKINS-30069] versionnumber plugin should resolve vars from "envinject" plugin

[jenkins-infra-bot]

versionnumber-plugin evaluates the environment variables before the envinject-plugin injects them, if the envinject-plugin is configured to inject them from a source file checked out from SCM.

The versionnumber-plugin has a "Version Number Format String" field which can take environment variables as the input. Trying to inject the variable, results in a blank evaluation of the variable, because it's instantiated from the SCM sourced file after the versionnumber-plugin.

It would be nice if to alter the order in which these plugins are run so they can work together.

---

Originally reported by rspring, imported from: versionnumber plugin should resolve vars from "envinject" plugin

• status: Open
• priority: Minor
• component(s): envinject-plugin, versionnumber-plugin
• resolution: Unresolved
• votes: 4
• watchers: 4
• imported: 20251216-225446

Raw content of original issue

versionnumber-plugin evaluates the environment variables before the envinject-plugin injects them, if the envinject-plugin is configured to inject them from a source file checked out from SCM.

The versionnumber-plugin has a "Version Number Format String" field which can take environment variables as the input.  Trying to inject the variable, results in a blank evaluation of the variable, because it's instantiated from the SCM sourced file after the versionnumber-plugin.

It would be nice if to alter the order in which these plugins are run so they can work together.

• environment: Jenkins version 1.609

[jenkins-infra-bot]

oleg_nenashev:

• Original comment link
• Raw content of original comment:

  Did you try to use "EnvInject" job property? Such case should be working in 1.92 
  

Did you try to use "EnvInject" job property? Such case should be working in 1.92

[jenkins-infra-bot]

rspring:

• Original comment link
• Raw content of original comment:

  There are several properties the EnvInject plugin has available in the job configuration.  However, even the very first configuration that can read a file from SCM, does so after the versionnumber-plugin evaluates the job environment variables.  Are you asking about a particular job property?
  

There are several properties the EnvInject plugin has available in the job configuration. However, even the very first configuration that can read a file from SCM, does so after the versionnumber-plugin evaluates the job environment variables. Are you asking about a particular job property?

[jenkins-infra-bot]

mdkf:

• Original comment link
• Raw content of original comment:

  I would like to be able to use the following in the version field:
  
  
  ${PROPFILE,file="JenkinsPropFile.txt",property="Version"}
  
  
  

I would like to be able to use the following in the version field:

${PROPFILE,file="JenkinsPropFile.txt",property="Version"}

[jenkins-infra-bot]

oleg_nenashev:

• Original comment link
• Raw content of original comment:

  No plan to work on it anytime soon. Pull requests will be appreciated, reviewed and integrated if possible.
  

No plan to work on it anytime soon. Pull requests will be appreciated, reviewed and integrated if possible.