-
Bug
-
Resolution: Unresolved
-
Major
-
None
With older Jenkins versions, the timestamp environment variable (formerly BUILD_ID) was
already set to the default timestamp format by the Jenkins core and was only modified by the Zen Timestamp plugin if the option "Change date pattern" was checked (inside the job or node configuration) and a different format was selected.
The new Zen plugin must be fixed to set the BUILD_TIMESTAMP variable in any case, even if there was no format defined inside the job or node configuration, by using the default timestamp format. This must be done by the plugin now, since BUILD_TIMESTAMP is not set by the core anymore.
- depends on
-
-
- Resolved
-
[JENKINS-29873] Zentimestamp should set BUILD_TIMESTAMP variable in any case
Michael Rentschler
created issue -
Michael Rentschler
made changes -
| Description | Original: With Jenkins 1.597, the environment variable {{BUILD_ID}} was changed from timestamp to the build number. The {{zentimestamp}} plugin can not alter the content of {{BUILD_ID}} anymore. A new environment variable should be introduced, like {{BUILD_TIMESTAMP}}. This can be modified by the plugin then. |
New:
With older Jenkins versions, the timestamp environment variable (formerly BUILD_ID) was already set to the default timestamp format by the Jenkins core and was only modified by the Zen Timestamp plugin if the option "Change date pattern" was checked (inside the job or node configuration) and a different format was selected. The new Zen plugin must be fixed to set the BUILD_TIMESTAMP variable in any case, even if there was no format defined inside the job or node configuration, by using the default timestamp format. This must be done by the plugin now, since BUILD_TIMESTAMP is not set by the core anymore. |
Michael Rentschler
made changes -
| Link |
New:
This issue depends on |
| Workflow | Original: JNJira [ 164950 ] | New: JNJira + In-Review [ 181757 ] |
