Skip to main content

How to discard Jenkins old builds from project or Pipeline?


When we work with Jenkins, we surely run our project(s) multiple times and this will result in a long queue of the build History list that mostly is of no use after certain numbers.

How to discard Jenkins old builds from project or Pipeline?

1) If you have access to the "Manage Jenkins" section of your Jenkins then you can run the below-mentioned script to clean your project Build History.
Note* This will reset the build number to 1 on your next run.

a) Access your Jenkins HP > Manage Jenkins > Script Console

b) Copy-Paste this script to your Console Script text area and update the "myproject_name" with your project name where you need to clean the build history and hit the "Run button".


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

This should clean your Build History for that particular project but if you're using the multi-branch pipeline, then you need to make the following changes in the above script:

def yourJobName = "path to your pipeline-'folder_name_job_name'"
def job = Jenkins.getInstance().getItemByFullName(yourJobName, Job.class)

Note* At times, if you still see your old builds on UI then after removing builds from the file system using above mentioned script you need to go to Manage Jenkins in the Jenkins GUI and click Reload Configuration from Disk.

2) If you don't have access to the "Manage Jenkins" section of your Jenkins, there is another way to remove old builds i.e. using a "discard-old-build" plugin where you can specify how many builds you want to keep and all older builds are discarded.
https://github.com/jenkinsci/discard-old-build-plugin

The best part of using this plugin is that the configuration settings allow for builds to be discarded based on age, quantity, intervals of these properties, status, log file size and expressions parsed from log files.


Resource Consulted: https://stackoverflow.com/


Labels:

Comments

Post a Comment

Popular posts from this blog

How to Unzip files in Selenium (Java)?

1) Using Java (Lengthy way) : Create a utility and use it:>> import java.io.BufferedOutputStream; import org.openqa.selenium.io.Zip; import java.io.File; import java.io.FileInputStream; import java.io.FileOutputStream; import java.io.IOException; import java.util.zip.ZipEntry; import java.util.zip.ZipInputStream;   public class UnzipUtil {     private static final int BUFFER_SIZE = 4096;     public void unzip (String zipFilePath, String destDirectory) throws IOException {         File destDir = new File(destDirectory);         if (!destDir.exists()) {             destDir.mkdir();         }         ZipInputStream zipIn = new ZipInputStream(new FileInputStream(zipFilePath));         ZipEntry entry = zipIn.getNextEntry();         // to iterates over entries in the zip folder         while (entry != null) {             String filePath = destDirectory + File.separator + entry.getName();             if (!entry.isDirectory()) {                 extractFile (zipIn, filePath);            
Post a Comment
Read more

Encode/Decode the variable/response using Postman itself

We get a lot of use cases where we may have to implement Base64 encoding and/or decoding while building our APIs. And, if you are wondering if it is possible to encode/decode the variable/response using Postman itself or how to encode/decode the token or password in postman and save it in a variable? To Base64 encode/decode, the quickest way is to use JavaScript methods btoa, atob: atob - It turns base64-encoded ASCII data back to binary. btoa - It turns binary data to base64-encoded ASCII. Sample code : var responseBody = pm.response.json(); var parsedPwd = JSON.parse(atob(responseBody.password)); // presuming password is in the payload pm.collectionVariables.set("password", parsedPwd);
Post a Comment
Read more

The use of Verbose attribute in testNG or POM.xml (maven-surefire-plugin)

At times, we see some weird behavior in your testNG execution and feel that the information displayed is insufficient and would like to see more details. At other times, the output on the console is too verbose and we may want to only see the errors. This is where a verbose attribute can help you- it is used to define the amount of logging to be performed on the console. The verbosity level is 0 to 10, where 10 is most detailed. Once you set it to 10, you'll see that console output will contain information regarding the tests, methods, and listeners, etc. <suite name="Suite" thread-count="5" verbose="10"> Note* You can specify -1 and this will put TestNG in debug mode. The default level is 0. Alternatively, you can set the verbose level through attribute in "maven-surefire-plugin" in pom.xml, as shown in the image. #testNG #automationTesting #verbose # #testAutomation
Post a Comment
Read more