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

BUILD_ID is defined to be the ID of the build, and the ID is now a number rather than a timestamp, so the current behavior is correct. (There are some things in Jenkins which expect a build ID.) Adding a new BUILD_TIMESTAMP variable for the dedicated purpose of representing time is the only option.
I would actually suggest two such variables:
Note that since builds may now come in at a rate of more than one per second, BUILD_TIMESTAMP_LEGACY could easily be nonunique.