-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Jenkins 1.510 (and previous)
Running within tomcat on linux environment with multiple slaves
When looking at the Modules page of a maven project I see that the last successful modules are at build number 425 (1 month ago), while the build history (panel on the left side) shows that last successful build is 440.
Restarting Jenkins did not help.
- duplicates
-
JENKINS-18846 New lazy loading permalinks can break job.lastStableBuild != null => job.lastSuccessfulBuild != null
- Resolved