-
Bug
-
Resolution: Fixed
-
Major
A user reported a situation with a project which had a number of builds, none of which had associated numeric symlinks because the master was running on Windows at the time. Then the master was switched to Unix. Jenkins created a lastSuccessfulBuild symlink, but it was pointing to a nonexistent numeric symlink. It should either avoid creating the permalink in this case, or first create the numeric symlink.
- is related to
-
JENKINS-18846 New lazy loading permalinks can break job.lastStableBuild != null => job.lastSuccessfulBuild != null
-
- Resolved
-
[JENKINS-19034] Permalinks can be created which point to a nonexistent build symlink
Link |
New:
This issue is related to |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Labels | Original: lazy-loading symlink | New: lazy-loading lts-candidate symlink |
Labels | Original: lazy-loading lts-candidate symlink | New: 1.509.4-rejected lazy-loading symlink |
Workflow | Original: JNJira [ 150481 ] | New: JNJira + In-Review [ 193541 ] |