|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-16023) Lazy loading causes... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading causes... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading causes... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading causes... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading causes... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading causes... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading causes... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading causes... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading causes... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading causes... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading causes... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading causes... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading causes... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading causes... [email protected] (JIRA)
- [JIRA] (JENKINS-16023) Lazy loading causes... [email protected] (JIRA)

<vlatombe> probably now that builds are fetched lazily, it may be worth to store some information at job level like lastSuccessFul/lastUnstableBuild/lastFailedBuild build numbers or timestamps
[14:26] <Johnou> yes I agree, doesn't make sense to load all jobs until it finds that information
[14:26] <Johnou> defeats the point of lazy init