Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

Plugin Information

View Zentimestamp on the plugin site for more information.

This plugin is up for adoption. Want to help improve this plugin? Click here to learn more!

This plugin export a BUILD_TIMESTAMP variable.


From Jenkins 1.597, the plugin adds the Jenkins BUILD_TIMESTAMP variable to the Configure System page of Manage Jenkins.  Note: you must activate the Global Property!
You must specify a java.text.SimpleDateFormat pattern such as the value 'yyyyMMddHHmmss'.


  • Export a BUILD_TIMESTAMP variable to the Jenkins instance (all jobs on all slaves will be impacted).
  • Export a BUILD_TIMESTAMP variable to the slave (all jobs on this slave will be impacted).
  • Export a BUILD_TIMESTAMP variable to the job (only the job will be impacted)


Release 4.2 (July 25, 2015)

Release 4.1 (May 24, 2015)

  • Commented out logging statement

Release 4.0 (April 07, 2015)

  • Fix JENKINS-26626 - Switch to use BUILD_TIMESTAMP environment variable and make it compatible with Jenkins 1.597+

Release 3.3 (May 16, 2013)

  • Fix JENKINS-17975 - SCM polling stops to work if the previously used build node no longer exists

Release 3.2 (March 10, 2012)

  • Make it compatible to MatrixProject

Release 3.1 (March 07, 2012)

Release 3.0 (December 21, 2011)

  • Add the ability to change the date format at node level

Release 2.2 (March 1, 2011)

  • Change UI labels from Hudson to Jenkins

Release 2.1 (February 19, 2011)

  • Updated over new Jenkins 1.397 API and metadata

Release 2.0.1 (July 02, 2010)

  • Fixed regression for backward compatibility with zentimestamp 1.2

Release 2.0 (June 20, 2010)

  • The plugin is now a job property that enables users to change the BUILD_ID variable from Hudson publishers too

Release 1.2 (February 10, 2009)

  • Upgraded to new Hudson API
  • Added integration tests

Release 1.1 (June 10, 2009)

  • Fixed Help 404 error with Hudson 1.3xx

Release 1.0 (August 12, 2008)

  • Initial release


  1. Unknown User (nhuth)

    I am trying to use this for a unique baseline with the CCplugin, but the format is current set after the workspace is prepared / directly after the baseline is created.  Is it planned to be able to be used on a Global level instead of a per job level or to have the formatting be the first action on the job or pre-job?


    1. Unknown User (gregoryboissinot)

      With Zentimestamp 2.0, you can change the format of the BUILD_ID variable for any build steps, any publishers and for any SCM actions (as for basline in the CC Hudson plugin).

  2. Unknown User (kvsn4u@gmail.com)

    Can we use this BUILD_ID variable in the email configuration as part of the content?

    1. Unknown User (nhuth)

      I was able to have the modified build_id sent out in an email.  I use the Email-ext plugin v2.8, Hud v1.382 by adding the following to global or job configuration: 

       ${ENV, var="BUILD_ID"}
    2. Unknown User (gbois)

      BUILD_ID variable is processed as a classic environment variable.
      Therefore, it depends of the email plugin content processing.

    3. Unknown User (gbois)

      Thanks Nick for your reply