[
https://issues.jenkins-ci.org/browse/JENKINS-12694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
gbois resolved JENKINS-12694.
-----------------------------
Resolution: Fixed
I'm sorry to not getting back to you sooner.
Zentimestamp plugin 3.0 used an extension point available only from Jenkins
1.410.
zentimestamp 3.1 is out. In this version, I remove the previous extension point
and use another compatible to Hudson 1.392 (before the fork in 1.398).
Therefore it is supposed to work.
Unfortunately, I didn't have tested.
Set issue to fix.
Thanks
> Zentimestamp plugin v3.0 no longer compatible with hudson.
> ----------------------------------------------------------
>
> Key: JENKINS-12694
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12694
> Project: Jenkins
> Issue Type: Bug
> Components: zentimestamp
> Reporter: Christopher Stephens
> Assignee: gbois
>
> As of version 3.0 the zen timestamp plugin appears to be no longer compatible
> with Hudson. I tested it in a stand alone Hudson instance (no additional
> plugins) against Hudson versions 2.2.0 and 2.1.0 and noticed that the
> BUILD_ID variable is not getting replaced by the correct pattern.
> I rolled back to version 2.2 of the plugin which appears to still be
> compatible with both versions of Hudson above.
> I did not see any errors in the logs when running projects with the plugin
> activated, only that the environment variable contained the original
> timestamp formatting.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
