|
||||||||
|
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.
@Peter Hackett: There was good reasons to use a different BUILD_ID than the timestamp. Using BUILD_TIMESTAMP instead should be a feasible change for everybody, not?
There is an alternative solution available. Please read my first comment above. This Groovy-one-liner will define a BUILD_TIMESTAMP variable.
The timestamp of this variable will match the exact time when Jenkins triggered the build (the time that will be shown in the build history of each job).
There is no jitter like its possible if you use the current time by calling e.g. 'date' from inside your build scripts.
Once this ticket is fixed, this workaround can be removed seamlessly.