-
Improvement
-
Resolution: Unresolved
-
Minor
At the moment the plug-in saves its output as environment variables. Instead, it could implement Token Macros (https://wiki.jenkins-ci.org/display/JENKINS/Token+Macro+Plugin) reusable by other plug-ins.
Would setting a token macro be a complete replacement for an environment variable, or just an addition?
With an envvar, you are able to use that data in a shell or groovy script for further processing. When setting a token macro, you can use the run-condition-plugin or conditional-buildstep, but it doesn't seem to be as featureful.
Am I missing something, or are there other considerations such as pipeline support where not messing with envvars is preferred?