I upgraded a system to Jenkins v1.509 and noticed a custom script breaks now which used to work fine. The reason seems to be a change which seems to have been introduced somewhere around v1.509 if I'm not mistaken.

Old behaviour:

1. ls -la /var/lib/jenkins/jobs/foo/lastSuccessful
   lrwxrwxrwx 1 jenkins nogroup 26 Feb 1 22:00 /var/lib/jenkins/jobs/foo/lastSuccessful -> builds/2013-02-01_22-00-34/

New behaviour:

1. ls -la /var/lib/jenkins/jobs/foo/lastSuccessful
   lrwxrwxrwx 1 jenkins nogroup 26 Apr 3 07:02 /var/lib/jenkins/jobs/foo/lastSuccessful -> builds/lastSuccessfulBuild/

People using the target's name of the symlink (like "2013-02-01_22-00-34" in my example) inside scripts for further processing might have broken scripts due to that change.

Could someone please confirm this change and the reason for that change?