[JENKINS-18992] rssChangeLog should be limited · jenkinsci/jenkins#14784

2013-07-29T21:37:52.000Z

https://jenkins.ci.cloudbees.com/job/core/job/jenkins_main_trunk/rssChangelog is 488K with 940 entries, which seems excessive. This seems to trigger JENKINS-10524 in some cases, and probably puts excessive load on the server and network. This URL also undermines lazy loading by loading all build records for a job. I think the feeds should be limited by default to, say, 20 entries. (RSS 0.91 limited feeds to 15, but we are using 2.0, or Atom.) Clients which really want a full-length feed can ask for it explicitly. --- Originally reported by jglick , imported from: rssChangeLog should be limited assignee : stefan_spieker status : Open priority : Major component(s) : core label(s) : lazy-loading, newbie-friendly, performance resolution : Unresolved votes : 0 watchers : 1 imported : 2025-11-24 Raw content of original issue https://jenkins.ci.cloudbees.com/job/core/job/jenkins_main_trunk/rssChangelog is 488K with 940 entries, which seems excessive. This seems to trigger JENKINS-10524 in some cases, and probably puts excessive load on the server and network. This URL also undermines lazy loading by loading all build records for a job. I think the feeds should be limited by default to, say, 20 entries. (RSS 0.91 limited feeds to 15, but we are using 2.0, or Atom.) Clients which really want a full-length feed can ask for it explicitly.

(5 comments) (0 reactions) (0 assignees)Java (25,266 stars) (9,474 forks)batch import

component:coreenhancementgood first issueimported-jira-issueperformancepriority:majorresolution:unresolved

説明

コントリビューターガイド

技術スタック: java
領域: backendperformance
Issue 種別: performance
難度: 2
推定時間: 1-3 hours
活動状況: stale
明確さ: clear
前提条件: Familiarity with JavaUnderstanding of Jenkins RSS feed generation
初心者向け度: 80
調査方針: Investigate how the RSS changelog is generated in Jenkins core, likely in classes such as `RSSFeed` or `Job`. The issue proposes limiting the default number of entries to 20 while allowing clients to request more via a query parameter. Look for existing constants or methods that define the feed size. Consider implementing a configuration option or simply capping the output. Reference the linked Jira issue and any related PRs if available.