|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
@ikeadam, yes, I'd like the plugin to support absolute or relative (to workspace) path, with support for token macros (variables). I'm not really asking for a new feature, as this support already exists. There's just a few lines of code that were introduced that skip the path resolution if the workspace was already deleted that I'd like to remove. I did a pull request for this here: https://github.com/jenkinsci/parameterized-trigger-plugin/pull/64