You need to enable JavaScript to run this app.
优惠活动
大模型
产品
解决方案
定价
更多

关于Jenkins Job Disk Usage指标含义的技术咨询

Understanding Jenkins Disk Usage Plugin's "Job Disk Usage" Metric

Hey there, let me break down exactly what the Job Disk Usage metric from the plugin covers, especially since you've noted it excludes build artifacts and workspaces:

  • Job configuration files: This includes the core config.xml for the job, plus any supplementary config files generated by plugins (like parameterized build settings, trigger configurations, or pipeline-specific configs if you're not pulling the Jenkinsfile from an SCM). Some complex jobs might also have subdirectories for nested configurations here.

  • Build history metadata (not artifacts): Every build under the builds/ directory in your job's folder contributes to this. Think about:

    • Build logs (build.log and any archived log files)
    • Build state records (build.xml which tracks build status, timestamps, trigger reasons, etc.)
    • Change set data (files that track SCM commit history associated with each build)
    • Plugin-generated build metadata (like test result summaries stored outside the workspace, or code quality check records)
  • Job-level plugin data: Many Jenkins plugins store persistent data directly in the job's directory rather than the workspace. For example:

    • Historical test report data that's retained across builds
    • Cached data from code analysis tools (like local scan results from quality plugins)
    • Notification history or audit logs tied specifically to the job
  • Archived non-artifact files: If you've configured any job-level archiving that's not part of the standard "Archive the artifacts" step (some plugins add custom archiving features), those files will be counted here too.

Quick way to verify:

Head to your Jenkins home directory (typically $JENKINS_HOME), navigate to jobs/<your-job-name> and run:

du -sh .

Then check subdirectories like builds/ or plugin-specific folders with the same command to pinpoint which part is eating up the space. A common culprit is hundreds of old builds with large logs—setting a build retention policy to delete older builds can quickly free up this space.

内容的提问来源于stack exchange,提问作者user2653926

相关产品推荐
方舟 Agent Plan

超全模态模型 × Harness 升级,最新支持 Deepseek-V4.1-Flash、GLM-5.3 系列、Doubao-Seedream-5.0-pro、Kimi-K3 (部分), 限时 9.9 元起

最近更新时间:2026.05.27 03:58:46