My apologies for not clearly defining the problem earlier. The build artifacts that are getting archived (and that should be controlled by the 'Discard Old Builds' setting) are not getting deleted despite setting the limit to any particular number (say, 10).
No issues with the workspace as it gets cleaned up before each build (as intended). Please provide any pointers regarding this. Thanks, Anubhaw On Apr 29, 3:36 am, Sami Tikka <[email protected]> wrote: > Jenkins does not store the builds in the workspace. > > When you configure Jenkins to archive build artifacts, they are copied away > from the workspace. These artifacts, and build logs and test results are > controlled by the Discard Old Builds setting. > > If you have old builds in the workspace, you probably have not set up > anything to clean the workspace from files from previous builds. You could > check the box under SCM settings to clean the workspace before building. > (This setting is in the SCM part of the job configuration because every SCM > plugin has their own way of doing it.) > > There is also a delete workspace plugin, which is useful for builds that do > not use SCM. > > -- Sami > > Anubhaw Shrivastav <[email protected]> kirjoitti 27.4.2012 kello > 15.52: > > > > > > > > > Hi everyone, > > > We have some jobs running on Jenkins configured to "Discard Old Builds", > > and despite setting "Max # of builds to keep" to 10 (or any other number > > for that matter), Jenkins is keeping a fat bunch of previous builds in > > workspace. > > > Please provide any insights. > > > Thanks, > > Anubhaw
