-
Bug
-
Resolution: Fixed
-
Major
I have seen this on some Maven module builds, especially ones where only some of the modules in the pom are build, e.g. by using `-pl some-module -am`
The MavenModuleSet will have both lastSuccessfulBuild and lastStableBuild defined.
The individual MavenModule instances, however, will only have lastStable defined.
- is blocking
-
JENKINS-16023 Lazy loading causes massive delays after a period of inactivity when loading dashboard
-
- Resolved
-
-
JENKINS-16089 Standard view columns interact force builds to be eagerly loaded
-
- Resolved
-
- is duplicated by
-
JENKINS-17534 Maven modules view not showing last successful build
-
- Resolved
-
- is related to
-
JENKINS-19034 Permalinks can be created which point to a nonexistent build symlink
-
- Resolved
-
-
JENKINS-21597 New Maven Plugin causes slowdown for huge multimodule projects
-
- Resolved
-
[JENKINS-18846] New lazy loading permalinks can break job.lastStableBuild != null => job.lastSuccessfulBuild != null
Link |
New:
This issue is duplicated by |
Link |
New:
This issue is related to |
Labels | New: lazy-loading lts-candidate permalink symlink |
Link |
New:
This issue is blocking |
Link |
New:
This issue is blocking |
Assignee | New: Jesse Glick [ jglick ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Labels | Original: lazy-loading lts-candidate permalink symlink | New: 1.509.4-fixed lazy-loading permalink symlink |
Link |
New:
This issue is related to |