|
||||||||
|
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.

Daniel Beck, my use-case is almost similar to Andrey's one.
We use an automatic reporting flows, which add job names to test classpathes. Since the parsing of BUILD_ID and JOB_NAME is a 'worst practice' in any case (formats may change at some point), the variable could be useful.
The main challenge is to select a proper variable name, because JOB_NAME has been already occupied.
IMO, MATRIX_PROJECT_NAME is a best option