Child pages
  • Disk Usage Plugin
Skip to end of metadata
Go to start of metadata

Plugin Information

View disk-usage on the plugin site for more information.

This plugin records disk usage.

Configuration

Showing disk usage trend graph is optional - unselect the "Show disk usage trend graph" checkbox on the global configuration page ("Manage Jenkins" -> "System configuration") if you don't want to see the graph on the project page.

Usage

When you install this plugin, disk usage is calculated each 60 minutes. You can see project list with occupied disk space by going to the "Disk Usage" page in the management section (Dashboard -> "Manage Jenkins" -> "Disk Usage"). The same page also allows you to schedule disk usage calculation immediately.


More detailed information can be seen on the project page, where you can find disk usage for each build and workspace, as well as a graph with disk usage trend.


Change Log

Upcoming changes

Release 0.29 (Coming soon)

Release 0.28 (Oct 01, 2015)

  • Remove excessive logging (JENKINS-30718)

Release 0.27 (September 21 2015)

  • Require admin permission to calculate disk space (JENKINS-23100)
  • Add disk usage as post-build step 

Release 0.26 (September 14 2015)

  • Fix bug where saving configuration resulted in multiple Job Config History entries (JENKINS-22224)
  •  

Release 0.25 (January 26, 2015)

  • Plugin doesn't rely on the format of Run.id any more (pull #26)

Release 0.24 (August 5, 2014)

Partially based on Git commit messages, it is difficult to pair them with Jira tasks.

  • Update disk usage changelog (JENKINS-20604)
  • Add workspace information in plugin main page
  • Separate not current slave wokrspace
  • Add current state into overall graph
  • Separate scale for workspaces
  • Enable excluded jobs for disk usage calculation
  • Fix size style on job page
  • Fix typo + move methods getValue and getUnit into ProjectDiskUsageActionFactory class

Release 0.23 (November 12, 2013)

Based on Git commit messages, it is difficult to pair them with Jira tasks.

  • Add test + fix bug which they catch and better line for graphAdd test + fix bug which they catch and better line for graph
  • Reverse build order in graph
  • Make graph huger
  • Make free space in job directory optional in global graph
  • Better sheduling automatic calculation
  • Move information about project disk usage form config.xml of job
  • Fixing typo direcotory -> directory
  • Display next execution time and add buttom for builds, jobs and workspaces
  • Fix link in menu on main page

Release 0.22 (October 18, 2013)

Based on Git commit messages, it is difficult to pair them with Jira tasks.

  • Fix tests - HudsonTestCase perform tests in the same jenkins home directory, so test have to do clean up
  • Fix test
  • Display all workspaces
  • Save history
  • Fix backward compatibility, fix concurent modification exception and make timeout workspace configurable
  • Replace Util.isSymlink
  • Fix backward compatibility
  • Control if diskUsageWithoutBuild!=null
  • Check if slaveWorkspacesUsage is not null
  • Change developer
  • Better colors for graph
  • Add backward compatibility
  • Add tests and fix bug which test find out
  • Correct information about author
  • Add tests for case the slave is deleted or workspace of project was deleted
  • Fix problems with claculation threads and removing workspaces form diskUsage set if do not exist or its slave does not exists
  • Add tests
  • Fix problems with symlinks
  • Add filter for builds age
  • Fix issue with graph
  • Add e-mail warnings
  • Configurable disk usage calculation
  • Another type of graph
  • Rewrite creation of graphs
  • Add funkcionality for counting disku usage of workspaces + tests
  • Change behaviour for counting jobs size and builds size + add tests for it
  • Rewriting disk-usage classes structure

Release 0.21 (September 9, 2013)

  • Added option for workspace calculation timeout configuration (pull #14)
  • Added French translation (pull #13)
  • Don't follow symlinks (pull #12)

Release 0.20 (June 5, 2013)

  • If workspace doesn't exists, use zero size instead of using previous workspace (pull #11)
  • Traditional Chinese translations (pull #10)

Release 0.19 (March 15, 2013)

  • Fixed link Jenkins management section (JENKINS-16420)
  • Fixed root link to preserve protocol (JENKINS-15565)
  • Fixed Compute maven module disk usage (JENKINS-15534)
  • Setup workspace timeout and added calculation of the build immediately after the build (pull #9)

Release 0.18 (September 4, 2012)

  • Fixed DiskUsage dont show values (JENKINS-14248)
  • Overall disk usage graph, removed some deprecated methods (pull #8

Release 0.17 (May 24, 2012)

  • Added support for hierachical job model (pull #6)
  • Fixed broken showGraph (pull #7

Release 0.16 (April 13, 2012)

Release 0.15 (February 26, 2012)

  • Migration from job property to project action which fixed couple of things (JENKINS-12870)
  • Link to disk usage plugin added to main page as /manage is restricted only for users with admin rights

Release 0.14 (June 27, 2011)

Release 0.13 (March 26, 2011)

  • Japanese translation 

Release 0.12 (Oct 22, 2010)

  • Bug fix - workspace disk usage shows wrong values in some cases (JENKINS-7867)

Release 0.11 (Jun 4, 2010)

Release 0.10 (Feb 10, 2010)

  • Update code for more recent Hudson

Release 0.9 (May 28, 2009)

  • Fixed a problem where prolonged disk usage computation can starve other timer activities, like polling.

Release 0.8:

  • Now works with Hudson ver. 1.293 (for details see JENKINS-3340)

Release 0.7:

  • ?

Release 0.6:

  • Added sum of values on the top of the overview page.
  • Disk usage for build is recalculated each time to reflect artifacts deletion.
  • Default trigger interval prolonged to 60 minutes.

Release 0.5:

  • Fixed "Back to Dashboard" link.
  • Added option for showing trend graph.
  • Fixed and reversed ordering on the overview page (the most space consuming projects are on the top of the page now).

Release 0.4:

  • Fixed NPE.

Release 0.3:

  • Icon changed.

Release 0.2:

  • First available public release.

Missing features and known bugs

23 Comments

  1. A summation of the values would be nice (first picture).

  2. Hi,

    just a question : did someone test this plugin work with master/slaves hudson ?

     How is it supposed to work ?

    1. Hi,
      yes, it should work with master/slave setup. Disk usage is taken from machine where the file is located (slave for workspace, master for build directory).

  3. Is there any changelog for Version 0.7?

    And could you please tell us more then "This plugin records disk usage." in the description of the plugin? The size of which folders are exactly shown in this statistics? It doesn't seem to be the "workspace" and the "build" folders of the jobs?!

    It would be a very good feature if this would show the size of

    1. the whole job-folder (thats the sum most will probably need to keep an eye on the jobs)
    2. the build-folder
    3. the modules-folder
    4. the workspace-folder

    Please change it or give me the possibility to change it on my own (wink)

    1. Hi,
      this is a wiki so feel free to add more information if you think it would be beneficial.

  4. It would be great to be able to sort table in first picture (to easily point projects taking the most disk space).

  5. Unknown User (jheckel@uillinois.edu)

    I do not see where the interval for checking disk usage is defined within Hudson or any configuration file.

    where is that?

    1. it's hardcoded in DiskUsageThread class, as the task which refresh disk usage extends AsyncPeriodicWork (and it's not possible to change the recurring timer once it has been setup)

  6. Unknown User (selena)

    This plugin is great but we had some difficulties adding it. CPU usage raised rocket high and was running two java.exe. Environment is Windows Server 2003 64bit AMD, JDK 1.5.22 for Hudson 1.364.

  7. It would be really nice to have global disk usage evolution on different nodes (1 chart per node for example)
    The same chart we have at the job level, but at the Hudson level (smile)

  8. Is it possible to trigger the calculation of the disk usage when commencing (or maybe after finishing) a build?

    I don't know why, but my graph doesn't look like the example above. It's more like ____/_/___/__ ;) It seems that some of the builds are not recorded at all. That makes it very difficult to recognize a trend.

  9. This plugin is really useful! It helped us to clean up lots of our projects which accumulated tons of outdated artifacts!

    Unfortunatelly we have to deinstall it for the time being... A single iteration takes ~6.5 hours, and iterations repeat each 6 hours unconditionally.

    It would be really nice to have an option to execute calculation only for those jobs which had new builds since last iteration. Or at least to make calculation periodicy tunable.

    Thanks

  10. Does anyone know why sometimes in 'plugin/disk-usage/' section as a result of calculating disk space I can see only '-' instead of correct number? Because of this situation I get unreliable graph.

    Greets.

  11. Is there a way to change the graph size? 350x150 is making it unreadable for us.

  12. Could you post the changelog for version 0.22 and 0.23?

  13. Bug report and change request:

    The disk usage for my project shows up on the project page like this:

    Disk Usage: Workspace 76 MB (On slaves 50 MB, Non slave workspaces 26 MB), Builds 181 MB (Locked -), Job directory 238 MB

    Firstly, the bug report: The figures above are obviously incorrect, because I'm not using any slaves. We have a single Jenkins server and that's all. So I would really like to know where it gets those figures from.

    Secondly, the change request: The text above is displayed on a single line. It is placed into Jenkins' right-hand side column in the project page, but is significantly wider than anything else in that column. It doesn't wrap, so it makes the whole column much wider than it needs to be, which causes layout glitches for the middle column. Could we please have the ability to specify the width of the text so we can make it fit better, or else have it wrap more sensibly. Thank you.

    1. Hi Simon, Please use the issues.jenkins-ci.org site to report issues. You can find the link to "Open Issues" at the top of the page.

      That way, there will be higher chances of having bugs fixed.

      1. Hi Jakub. Thanks for the reply. I have logged JENKINS-25716 and JENKINS-25715 for you.

  14. This plugin uses biggest amount of jenkins server RAM
    Screenshot RAM usage before and after removal this plugin

    http://i68.fastpic.ru/big/2015/1007/80/fd7185293676d0b8225773c4d98a0380.png

  15. There seems to be something wrong with builds that do not keep their artifacts. The disk usage keeps showing the usage with the artifacts.

    I only keep the artifacts of the last successful build. So, for instance, my latest build 145 has a size of 529Mb. It has artifacts and if I check the disk, then that is correct.

    Build 143 however doesn't have its artifacts anymore, but it still says the disk usage is 529Mb. On disk it's 180KB.

    This has only been happening since recently, maybe because I changed configuration. But is this intended behavior? Because now, the Disk Usage Trend just isn't correct...

    If you need logs or screenshots, let me know.

  16. There seems to be something wrong with builds that do not keep their artifacts. The disk usage keeps showing the usage with the artifacts.

    I only keep the artifacts of the last successful build. So, for instance, my latest build 145 has a size of 529Mb. It has artifacts and if I check the disk, then that is correct.

    Build 143 however doesn't have its artifacts anymore, but it still says the disk usage is 529Mb. On disk it's 180KB.

    This has only been happening since recently, maybe because I changed configuration. But is this intended behavior? Because now, the Disk Usage Trend just isn't correct...

    If you need logs or screenshots, let me know.

  17. There seems to be something wrong with builds that do not keep their artifacts. The disk usage keeps showing the usage with the artifacts.

    I only keep the artifacts of the last successful build. So, for instance, my latest build 145 has a size of 529Mb. It has artifacts and if I check the disk, then that is correct.

    Build 143 however doesn't have its artifacts anymore, but it still says the disk usage is 529Mb. On disk it's 180KB.

    This has only been happening since recently, maybe because I changed configuration. But is this intended behavior? Because now, the Disk Usage Trend just isn't correct...

    If you need logs or screenshots, let me know.

  18. Will 0.29 ever be released or can we safely consider this plugin dead?