Estimate disk space consumed by Jenkins job workspaces across concurrent builds.
Each Jenkins agent that checks out a job maintains its own workspace on local disk containing the repository, any build output left behind, and downloaded dependencies — and because workspaces aren't shared across agents by default, the same job's workspace footprint is effectively duplicated on every agent capable of running it. Total fleet-wide workspace storage is therefore the per-agent footprint multiplied by agent count, with dependency caches (node_modules, Maven .m2, pip/conda caches) very often the single largest contributor.
totalWorkspace = agents × (repoSize + buildOutput + depsCache)
Package ecosystems like npm/Maven/pip resolve full transitive dependency trees onto disk, and unlike source code these caches often include many versions or unused transitive packages, routinely dwarfing the actual application source and build output.
It frees disk between builds but increases build time, since dependency caches and incremental build state get discarded too — most teams instead clean build output between builds while persisting dependency caches to balance disk usage against speed.
Use shallow git clones instead of full history, route large dependency caches to a shared network cache or artifact proxy (e.g. a local npm/Maven mirror) instead of re-downloading per agent, and clean build output directories after archiving artifacts.