I hope Macros will also work on release input.

I hope the macro will work on release input as well.

scenario.
1. Add a CollabNet file release to the post-build action.
2. Enter the project, package, and release.
3. Use the $ {BUILD_NO} macro in the release area.
4. Check the files uploaded to Team Forge since the success of Jenkins build.
5. The release name is entered as '$ {BUILD_NO}'.

idea.
I want to use the CollabNet plugin to improve the input when creating a release.
Please upgrade to use macros.

by: Sangyun K. | over a year ago | File Releases

Comments

• This is the idea that came up on the Jenkins CollabNet plugin page six years ago.
  But it has not been developed yet.

  by: Sangyun K. | over a year ago

• when doing so, ensure that it can be used in pipelines

  by: Lutz W. | over a year ago

• No, it's disabled.

  by: Sangyun K. | over a year ago

• Macros or env. variables in fields such as release names, packages, ... are a must have. Otherways the Jenkins job has to be changed again and again. The plug in as it exists today does not really support continuous integration.

  by: Johannes L. | over a year ago

• +Johannes L, You're right!

  by: Sangyun K. | over a year ago