Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Minor
-
Resolution: Won't Fix
-
Component/s: core
-
Labels:None
-
Environment:Since version 1.597
-
Similar Issues:
Description
With this release jenkins changed the build identifier to the build number (instead of timestamp). Now the BUILD_NUMBER and BUILD_ID both return the build number and there is no way to get the timestamp from the environment variables.
According to the documentation BUILD_ID should return the timestamp.
BUILD_ID
The current build id, such as "2005-08-22_23-59-59" (YYYY-MM-DD_hh-mm-ss)
Possible fixes:
- Change BUILD_ID to return the timestamp
- Add Env-Var BUILD_TIMESTAMP or similar
Attachments
Issue Links
- is duplicated by
-
JENKINS-26624 Content of BUILD_ID environment variable changed from timestamp to build number
-
- Resolved
-
-
JENKINS-26679 BUILD_ID not containing build timestamp after 1.597 due to JENKINS-24380
-
- Resolved
-
-
JENKINS-26772 env-vars.html BUILD_ID documentation is incorrect
-
- Resolved
-
- is related to
-
JENKINS-26626 Zentimestamp plugin no longer compatible with Jenkins 1.597
-
- Resolved
-
-
JENKINS-24380 Use build numbers as IDs
-
- Resolved
-
- links to
@Chris
There is still a bug inside the ZenTimestamp Plugin. Once this is fixed, you do not have to check this option in every Jenkins job configuration.
It should be enough to install the ZenTimestamp plugin. Then the BUILD_TIMESTAMP variable will be set to its default format.
So far, until this issue inside the ZenTimestamp plugin was fixed, you have to set it in every job config (like you noticed).
Or, as a simple workaround, set the ZenTimestamp format on the global Jenkins configuration page. That option should apply for all jobs then. (Jeff was faster here
Once the plugin was fixed, even this check box is not necessary anymore. See the last comments on the reopened issue
JENKINS-26626