possible to switch back to using timestamps instead of build numbers in jobs folder

[BeckyY]

I recently upgraded Jenkins and noticed build artifacts folder names have switched to using job numbers instead of timestamps.   Does anyone know if it is possible to keep the upgrade but configure Jenkins to use timestamps instead of job numbers for the artifacts folder names for each saved build?

[Baptiste Mathus]

Hi,

I don't think it is. And looking at the doc: https://wiki.jenkins-ci.org/display/JENKINS/JENKINS-24380+Migration if you want to go back it's supported but only to run a previous Jenkins version.

So, the question is: what would you want to have that format back?

Cheers

2015-09-02 19:30 GMT+02:00 BeckyY <rebe...@amdocs.com>:

I recently upgraded Jenkins and noticed build artifacts folder names have switched to using job numbers instead of timestamps.   Does anyone know if it is possible to keep the upgrade but configure Jenkins to use timestamps instead of job numbers for the artifacts folder names for each saved build?

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/4b1d292d-c345-43d9-9f83-c18100533bc7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

[BeckyY]

Thank you, Baptiste!   I have scripts that peruse the artifacts directory and perform certain actions, expecting the builds to be in order from a simple ant fileset usage.   With timestamp named dirs, the perusal was always in correct sequence.  Now it's not, as build 99 is ordered as later than build 103, for example.   We've used these scripts for years and there will be quite a large number to update to now work with this new format.