[JENKINS-65619] Allow plot plugin source CSV name to include environment variables

[jenkins-infra-bot]

The plot plugin allows you to specify a filename for the source data. It would be very useful if this was able to include environment variables as filenames on some other post build steps and plugins do (e.g. the "Archive the artifacts" option, or the obsolete "Copy To Slave" plugin)

 

This would allow a CSV file name like "${JOB_NAME}_data.csv" to work, which currently doesn't

 

That would then allow the plot configuration to be copied more easily when creating a new job as a "Copy from existing" option

---

Originally reported by firthmj, imported from: Allow plot plugin source CSV name to include environment variables

• assignee: vgaidarji
• status: Open
• priority: Minor
• component(s): plot-plugin
• resolution: Unresolved
• votes: 1
• watchers: 2
• imported: 20260512-210953

Raw content of original issue

The plot plugin allows you to specify a filename for the source data. It would be very useful if this was able to include environment variables as filenames on some other post build steps and plugins do (e.g. the "Archive the artifacts" option, or the obsolete "Copy To Slave" plugin)

 

This would allow a CSV file name like "${JOB_NAME}_data.csv" to work, which currently doesn't

 

That would then allow the plot configuration to be copied more easily when creating a new job as a "Copy from existing" option

[jenkins-infra-bot]

jielpe_fr38:

• Original comment link
• Raw content of original comment:

  This would really be a good feature, for example when a developer wants to include such a step into a global lib custom step which both publish some results and display a corresponding trend. There is no reason for the csv file to have the same name whatever the type of data it records or the job which creates it. So, using a var in the name is obviously a must have.
  

This would really be a good feature, for example when a developer wants to include such a step into a global lib custom step which both publish some results and display a corresponding trend. There is no reason for the csv file to have the same name whatever the type of data it records or the job which creates it. So, using a var in the name is obviously a must have.