Currently, the baseline name pattern (I will use the word "pattern" instead of "template" to avoid confusion) can include the following "variables" (taken straight from the help for the form field) :
- [PROJECTID] includes the name of the Dimensions CM project or stream being monitored into the baseline name.
- [HUDSON_PROJECT] includes the name of the Jenkins project / job name into the baseline name.
- [DM_BASELINE] includes the build variable ${DM_BASELINE} into the baseline name.
- [BUILDNO] includes the Jenkins job build number into the baseline name.
- [CURRENT_DATE] includes the current date in
"yyyy.MMMMM.dd hh:mm:ss aaa z" format, e.g. "2010.May.15 12:15:01 PM BST", into the baseline name.
For example, the baseline name pattern
[PROJECTID]_I_[HUDSON_PROJECT]_D_[BUILDNO]_C_[CURRENT_DATE]
might create a baseline with a name like
QLARIUS:JAVADEV_I_JAVADEV_hudson_D_10_C_2010.May.08 11:10:11 PM BST
If you specify a baseline name pattern that contains no variables in it, then the pattern will be used directly as the baseline name.
Note the variables in the baseline name pattern are not specified in the standard "${VARIABLE_NAME}" format used elsewhere in Jenkins, but as "[VARIABLE_NAME]" instead, and you can only use these specific variable names.
–
I believe that this new issue is asking for the above functionality to be extended to allow arbitrary build variables that have been defined on the Jenkins job to also be used in the baseline name pattern, as well as the above fixed variable names?
If so, then that sounds like a very reasonable improvement request and should not be too hard to implement quickly. Can you confirm?
As a workaround in the meantime, note that if you add a build variable to the job called DM_BASELINE then you can refer to this one specific build variable in the baseline name pattern using "[DM_BASELINE]".
Currently, the baseline name pattern (I will use the word "pattern" instead of "template" to avoid confusion) can include the following "variables" (taken straight from the help for the form field) :
"yyyy.MMMMM.dd hh:mm:ss aaa z" format, e.g. "2010.May.15 12:15:01 PM BST", into the baseline name.
For example, the baseline name pattern
[PROJECTID]_I_[HUDSON_PROJECT]_D_[BUILDNO]_C_[CURRENT_DATE]
might create a baseline with a name like
QLARIUS:JAVADEV_I_JAVADEV_hudson_D_10_C_2010.May.08 11:10:11 PM BST
If you specify a baseline name pattern that contains no variables in it, then the pattern will be used directly as the baseline name.
Note the variables in the baseline name pattern are not specified in the standard "${VARIABLE_NAME}" format used elsewhere in Jenkins, but as "[VARIABLE_NAME]" instead, and you can only use these specific variable names.
–
I believe that this new issue is asking for the above functionality to be extended to allow arbitrary build variables that have been defined on the Jenkins job to also be used in the baseline name pattern, as well as the above fixed variable names?
If so, then that sounds like a very reasonable improvement request and should not be too hard to implement quickly. Can you confirm?
As a workaround in the meantime, note that if you add a build variable to the job called DM_BASELINE then you can refer to this one specific build variable in the baseline name pattern using "[DM_BASELINE]".