|
||||||||
|
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.
Jesse, What are your plans in respect of this issue?
I've applied the Groovy script workaround to inject BUILD_TIMESTAMP into my builds and have adjusted usage of BUILD_ID to match. That all works fine.
If that is going to be the recommended way to fixup affected systems then personally I am fine with that and I would suggest that this issue will be closed as will not fix with the workaround documented.
If the intention is to add a BUILD_TIMESTAMP variable parallel to BUILD_ID then I will adapt my earlier fix if you do not have the bandwidth to do that.