|
||||||||
|
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/groups/opt_out.
Yeah, this makes a lot of sense.
To be honest, I thought you got this "for free" with Jenkins since I have done similar stuff with other plugins. Didn't realize they were using the "token macro" plugin.
Regarding functionality, because 'trigger tokens' are directly tied to jobs, would it make sense to just have everything be tokenized, or does that sound unnecessary?