-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins-2.7.2, plugin 1.15 (latest)
It seems that variables are not expanded in the "Files to parse" field which limits the use of the plugin in some cases. E.g. the following doesn't work:
Files to parse = somepath/${AVAR}/*.xml
Sorry if I missed it.
Cheers,
Phil.
[JENKINS-37902] Summary Display Plugin Does not Expand Variables used in "Files to parse"
Description |
Original:
It seems that variables are not expanded in the "Files to parse" field which limits the use of the plugin in some cases. E.g. the following doesn't work: _*Files to parse* = /my/path/${AVAR}/*.xml_ Sorry if I missed it. Cheers, Phil. |
New:
It seems that variables are not expanded in the "Files to parse" field which limits the use of the plugin in some cases. E.g. the following doesn't work: *Files to parse = /my/path/${AVAR}/\*.xml* Sorry if I missed it. Cheers, Phil. |
Description |
Original:
It seems that variables are not expanded in the "Files to parse" field which limits the use of the plugin in some cases. E.g. the following doesn't work: *Files to parse = /my/path/${AVAR}/\*.xml* Sorry if I missed it. Cheers, Phil. |
New:
It seems that variables are not expanded in the "Files to parse" field which limits the use of the plugin in some cases. E.g. the following doesn't work: {code}Files to parse = /my/path/${AVAR}/*.xml{code} Sorry if I missed it. Cheers, Phil. |
Description |
Original:
It seems that variables are not expanded in the "Files to parse" field which limits the use of the plugin in some cases. E.g. the following doesn't work: {code}Files to parse = /my/path/${AVAR}/*.xml{code} Sorry if I missed it. Cheers, Phil. |
New:
It seems that variables are not expanded in the "Files to parse" field which limits the use of the plugin in some cases. E.g. the following doesn't work: {code}Files to parse = somepath/${AVAR}/*.xml{code} Sorry if I missed it. Cheers, Phil. |