![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Unassigned |
|
Components:
|
core |
|
Created:
|
03/Apr/13 1:00 PM
|
|
Description:
|
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:
- 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:
- 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?
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Michael Prokop
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
