-
Bug
-
Resolution: Fixed
-
Major
LastFailureColumn, shown by default in AllView, is calling Job.getLastFailedBuild which then keeps on loading builds until it finds a failed build, with no cutoff. The fix for that would be to either impose a maximum number of builds to search back from (10? 20?); or do the search asynchronously after the page loads, which might still put some load on the server but would at least not stop you from browsing.
The same would apply to the last success column if all your recent builds failed, etc.
- depends on
-
JENKINS-18846 New lazy loading permalinks can break job.lastStableBuild != null => job.lastSuccessfulBuild != null
-
- Resolved
-
- is blocking
-
JENKINS-16023 Lazy loading causes massive delays after a period of inactivity when loading dashboard
-
- Resolved
-
-
JENKINS-8754 ROADMAP: Improve Start-up Time
-
- Closed
-
- is related to
-
JENKINS-17449 Jenkins 1.509 has different behaviour with symlink handling of e.g. lastSuccessful
-
- Resolved
-
In fs jenkins have some symlinks like 'lastStable' or 'lastSuccessful'. May be good point is to create other 'last<Failure|Unstable|whatever' and use these links when load jobs in view.
Also build.xml is to heavy to parse it only for few columns displayed on page. Possibly creating an light json file with only required info also improves performance.