-
Bug
-
Resolution: Fixed
-
Minor
-
None
If you set the external builds directory for Jenkins to e.g. /tmp/builds/${ITEM_FULL_NAME} and build some job, you will get a symlink /tmp/builds/lastStable pointing to builds/2013-... which does not exist. The symlink should be created in the job's root directory, as it would be if the builds dir were not set (except with an absolute target path in this case).
- is blocking
-
JENKINS-8446 'builds' directory in a separate location?
-
- Closed
-
- is duplicated by
-
JENKINS-12501 LastStable and LastSuccessful symbolic links created in wrong location if Build Record Root Directory does not end in builds
-
- Resolved
-
- is related to
-
JENKINS-17138 Deleting/renaming jobs using external builds directory does not move builds
-
- Resolved
-
- relates to
-
JENKINS-37862 Extract build symlink handling to a plugin
-
- Resolved
-
Code changed in jenkins
User: Jesse Glick
Path:
changelog.html
core/src/main/java/hudson/model/AbstractBuild.java
test/src/test/java/hudson/model/AbstractProjectTest.java
http://jenkins-ci.org/commit/jenkins/b90b20227e7e2497856404a1ca4e771e282504ff
Log:
[FIXED JENKINS-17137] Bogus permalinks created when using external builds directory.
Compare: https://github.com/jenkinsci/jenkins/compare/400fa878e66c...b90b20227e7e
–
You received this message because you are subscribed to the Google Groups "Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.