92

I recently updated the configuration of one of my hudson builds. The build history is out of sync. Is there a way to clear my build history?

Please and thank you

Sergio
  • 3,317
  • 5
  • 32
  • 51
Mahdi Yusuf
  • 19,931
  • 26
  • 72
  • 101

17 Answers17

119

Use the script console (Manage Jenkins > Script Console) and something like this script to bulk delete a job's build history https://github.com/jenkinsci/jenkins-scripts/blob/master/scriptler/bulkDeleteBuilds.groovy

That script assumes you want to only delete a range of builds. To delete all builds for a given job, use this (tested):

// change this variable to match the name of the job whose builds you want to delete
def jobName = "Your Job Name"
def job = Jenkins.instance.getItem(jobName)

job.getBuilds().each { it.delete() }
// uncomment these lines to reset the build number to 1:
//job.nextBuildNumber = 1
//job.save()
rjohnston
  • 7,153
  • 8
  • 30
  • 37
  • 5
    Great!! definitely the best approach! :) – hek2mgl Nov 07 '13 at 10:16
  • great trick, but how about resetting the build counter? any scripting for that? – Jes Chergui May 14 '15 at 09:15
  • 1
    @JesChergui I've updated to show resetting the build number. The script console lets you control all sorts of things, see http://javadoc.jenkins-ci.org/ (AbstractProject is a good place to start for playing with jobs) – rjohnston May 14 '15 at 23:49
  • My Jenkins complained that it wasn't allowed to access instances, or such like. I was running it from a new pipeline I'd setup specifically for this deletion and I pasted in the code above and changed the name. – Will Jan 18 '17 at 07:45
  • @Will this is due to the script security plugin which puts pipeline jobs in a super restrictive sandbox. See if you have a signature to approve under "Manage Jenkins" > "In-process script approvals". Another option would be to use the Scriptler plugin's ability to run admin scripts in a job: https://wiki.jenkins-ci.org/display/JENKINS/Scriptler+Plugin – rjohnston Jan 18 '17 at 09:58
  • I am getting this error ; `java.lang.NullPointerException: Cannot invoke method getBuilds() on null object` – muhammed ozbilici Apr 09 '20 at 13:22
  • @muhammedozbilici try using Jenkins.instance.getItemByFullName instead of Jenkins.instance.getItem – Michael Platings May 24 '20 at 08:02
  • @Michael Platings actually, it was about script console security, you have to approve these methods. – muhammed ozbilici May 25 '20 at 11:16
84

This answer is for Jenkins

  1. Go to your Jenkins home page → Manage JenkinsScript Console

    Enter image description here

  2. Run the following script there. Change copy_folder to your project name

Code:

def jobName = "copy_folder"
def job = Jenkins.instance.getItem(jobName)
job.getBuilds().each { it.delete() }
job.nextBuildNumber = 1
job.save()

My post

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
Nayana Adassuriya
  • 23,596
  • 30
  • 104
  • 147
51

If you click Manage Hudson / Reload Configuration From Disk, Hudson will reload all the build history data.

If the data on disk is messed up, you'll need to go to your %HUDSON_HOME%\jobs\<projectname> directory and restore the build directories as they're supposed to be. Then reload config data.

If you're simply asking how to remove all build history, you can just delete the builds one by one via the UI if there are just a few, or go to the %HUDSON_HOME%\jobs\<projectname> directory and delete all the subdirectories there -- they correspond to the builds. Afterwards restart the service for the changes to take effect.

Nielsm
  • 289
  • 1
  • 5
  • 18
William Leara
  • 10,595
  • 4
  • 36
  • 58
  • I have deleted all files and folders inside "/var/lib/jenkins/jobs/Demo" but I when go to Jenkins UI inside this JOB I still see builds history. – paul Apr 02 '14 at 07:10
  • 1
    After you "monkey" with the directory structure, just go to "Manage Jenkins" and select "Reload Configuration From Disk" – DanBaker Oct 03 '14 at 15:21
  • 1
    @paul, after delete the folders there, a **restart** of Jenkins is needed to see the build history disappeared from the UI. BTW, if we're using Jenkins, the path is typically located at /var/jenkins_home/jobs/{project name}/builds/ – Bright Jun 09 '16 at 02:42
  • I think this solution requires to much steps on the system side, a much more clean solution is provided in the answer from @Nayana Adassuriya – lfn Sep 11 '18 at 21:41
24

Here is another option: delete the builds with cURL.

$ curl -X POST http://jenkins-host.tld:8080/jenkins/job/myJob/[1-56]/doDeleteAll

The above deletes build #1 to #56 for job myJob.

If authentication is enabled on the Jenkins instance, a user name and API token must be provided like this:

$ curl -u userName:apiToken -X POST http://jenkins-host.tld:8080/jenkins/job/myJob/[1-56]/doDeleteAll

The API token must be fetched from the /me/configure page in Jenkins. Just click on the "Show API Token..." button to display both the user name and the API token.

Edit: one might have to replace doDeleteAll by doDelete in the URLs above to make this work, depending on the configuration or the version of Jenkins used.

Erwan Legrand
  • 4,148
  • 26
  • 26
  • Super useful, thank you! This is the only answer (on this question anyway) which allows for selective deletion, for instance when you discover a job that wasn't previously configured to discard old builds and want to get rid of a lot (but not all) of history. – Chris Hillery Mar 17 '22 at 02:50
12

Here is how to delete ALL BUILDS FOR ALL JOBS...... using the Jenkins Scripting.

def jobs = Jenkins.instance.projects.collect { it } 
jobs.each { job -> job.getBuilds().each { it.delete() }} 
benbenw
  • 723
  • 7
  • 20
ort11
  • 3,359
  • 4
  • 36
  • 69
9

You could modify the project configuration temporarily to save only the last 1 build, reload the configuration (which should trash the old builds), then change the configuration setting again to your desired value.

the_mandrill
  • 29,792
  • 6
  • 64
  • 93
  • Sorry, haven't used Hudson now for a couple of years, but see this about reloading the configuration: http://stackoverflow.com/questions/5216552/does-anyone-know-how-to-reload-hudson-configuration-without-restarting – the_mandrill Feb 26 '14 at 22:41
  • As someone who does not have admin permissions to Jenkins, this was the only option that worked for me. – DrStrangepork Jan 30 '19 at 21:36
7

If you want to clear the build history of MultiBranchProject (e.g. pipeline), go to your Jenkins home page → Manage Jenkins → Script Console and run the following script:

def projectName = "ProjectName"
def project = Jenkins.instance.getItem(projectName)
def jobs = project.getItems().each {
  def job = it
  job.getBuilds().each { it.delete() }
  job.nextBuildNumber = 1
  job.save()
}
metala
  • 71
  • 1
  • 5
7

This one is the best option available.

Jenkins.instance.getAllItems(AbstractProject.class).each {it -> Jenkins.instance.getItemByFullName(it.fullName).builds.findAll { it.number > 0 }.each { it.delete() } }

This code will delete all Jenkins Job build history.

Rahul khanvani
  • 373
  • 3
  • 13
  • 3
    For anyone wondering how to run the above code, go to Jenkins Home > Manage Jenkins > Script Console. There will be a text field there that you can enter this script into. – Pharaoh Tools Mar 28 '19 at 16:38
  • jenkins 2.293 returned the job names but builds were not removed – JRichardsz Jul 14 '22 at 22:44
3

Using Script Console.

In case the jobs are grouped it's possible to either give it a full name with forward slashes:

getItemByFullName("folder_name/job_name") 
job.getBuilds().each { it.delete() }
job.nextBuildNumber = 1
job.save()

or traverse the hierarchy like this:

def folder = Jenkins.instance.getItem("folder_name")
def job = folder.getItem("job_name")
job.getBuilds().each { it.delete() }
job.nextBuildNumber = 1
job.save()
ATrubka
  • 3,982
  • 5
  • 33
  • 52
2

Deleting directly from file system is not safe. You can run the below script to delete all builds from all jobs ( recursively ).

def numberOfBuildsToKeep = 10
Jenkins.instance.getAllItems(AbstractItem.class).each {
  if( it.class.toString() != "class com.cloudbees.hudson.plugins.folder.Folder" && it.class.toString() != "class org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject") {
    println it.name
    builds = it.getBuilds()
    for(int i = numberOfBuildsToKeep; i < builds.size(); i++) {
        builds.get(i).delete()
      println "Deleted" + builds.get(i)
    }
  }
}
geisterfurz007
  • 5,292
  • 5
  • 33
  • 54
Aytunc Beken
  • 111
  • 6
2

Go to "Manage Jenkins" > "Script Console"

Run below:

def jobName = "build_name"  
def job = Jenkins.instance.getItem(jobName)  
job.getBuilds().each { it.delete() }  
job.save()
msahin
  • 1,520
  • 1
  • 16
  • 22
1

Another easy way to clean builds is by adding the Discard Old Plugin at the end of your jobs. Set a maximum number of builds to save and then run the job again:

https://wiki.jenkins-ci.org/display/JENKINS/Discard+Old+Build+plugin

Rutger Huijsmans
  • 2,330
  • 2
  • 30
  • 67
1

Go to the %HUDSON_HOME%\jobs\<projectname> remove builds dir and remove lastStable, lastSuccessful links, and remove nextBuildNumber file.

After doing above steps go to below link from UI
Jenkins-> Manage Jenkins -> Reload Configuration from Disk

It will do as you need

Manish Agrawal
  • 794
  • 1
  • 9
  • 23
1

If using the Script Console method then try using the following instead to take into account if jobs are being grouped into folder containers.

def jobName = "Your Job Name"
def job = Jenkins.instance.getItemByFullName(jobName)

or

def jobName = "My Folder/Your Job Name
def job = Jenkins.instance.getItemByFullName(jobName)
0

Navigate to: %JENKINS_HOME%\jobs\jobName

Open the file "nextBuildNumber" and change the number. After that reload Jenkins configuration. Note: "nextBuildNumber" file contains the next build no that will be used by Jenkins.

Andreas
  • 5,393
  • 9
  • 44
  • 53
Nitish
  • 1
0

Tested on jenkins 2.293 over linux. It will remove all the build logs but not the corellative build number

cd /var/lib/jenkins/jobs
find . -name "builds" -exec rm -rf {} \;

Be careful with this command because it executes a rm -rf on each find result. You could exec this first to validate if the result are only the builds folder of you jobs

find . -name "builds"
JRichardsz
  • 14,356
  • 6
  • 59
  • 94
0

If you are looking for a solution where you have job inside a Folder you can use getItemByFullName function. It also supports white space in folder and job name.

def jobName = "folder_name/job_name"
def job = Jenkins.instance.getItemByFullName(jobName)
job.getBuilds().each { it.delete() }
job.nextBuildNumber = 1
job.save()
Shivam Anand
  • 952
  • 1
  • 10
  • 21