Databases
StackOverflow2013
Postsdbo
PODo not delete a Jenkins build if it's marked as "Keep this build forever" - Groovy script to delete Jenkins builds
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODo not delete a Jenkins build if it's marked as "Keep this build forever" - Groovy script to delete Jenkins builds
    primarykey
    data
    text
    <p>I have the following Groovy script which deletes all builds of a given Jenkins job except one build number that user provides (i.e. wants to retain).</p> <pre><code>/*** BEGIN META { "name" : "Bulk Delete Builds except the given build number", "comment" : "For a given job and a given build number, delete all build except the user provided one.", "parameters" : [ 'jobName', 'buildNumber' ], "core": "1.409", "authors" : [ { name : "Arun Sangal" } ] } END META **/ // NOTE: Uncomment parameters below if not using Scriptler &gt;= 2.0, or if you're just pasting the script in manually. // ----- Logic in this script takes 5000 as the infinite number, decrease / increase this value from your own experience. // The name of the job. //def jobName = "some-job" // The range of build numbers to delete. //def buildNumber = "5" def lastBuildNumber = buildNumber.toInteger() - 1; def nextBuildNumber = buildNumber.toInteger() + 1; import jenkins.model.*; import hudson.model.Fingerprint.RangeSet; def jij = jenkins.model.Jenkins.instance.getItem(jobName); println("Keeping Job_Name: ${jobName} and build Number: ${buildNumber}"); println "" def setBuildRange = "1-${lastBuildNumber}" def range = RangeSet.fromString(setBuildRange, true); jij.getBuilds(range).each { it.delete() } println("Builds have been deleted - Range: " + setBuildRange) setBuildRange = "${nextBuildNumber}-5000" range = RangeSet.fromString(setBuildRange, true); jij.getBuilds(range).each { it.delete() } println("Builds have been deleted - Range: " + setBuildRange) </code></pre> <p>This works well for any Jenkins job. For ex: If your Jenkins job name is "TestJob" and you have 15 builds i.e. build# 1 to build 15 in Jenkins, and you want to delete all but retain build# 13, then this script will delete the builds (build# 1-12 and 14-15 - even if you mark any build as "Keep this build forever") and only keep build#13.</p> <p><br/> <strong>Now, what I want is:</strong><br/></p> <ol> <li><p>what should I change in this script to not delete a build - if a build is marked in Jenkins as "Keep this build forever". I tried the script and it deleted that keep forever build too.</p></li> <li><p>Lets say, if I'm using "Build name setter plugin" in Jenkins, which can give me build names as what name I want i.e. instead of getting just build as build#1 or #2, or #15, I will get build as build# 2.75.0.1, 2.75.0.2, 2.75.0.3, ..... , 2.75.0.15 (as I would have set the build name/description as use some variable which contains 2.75.0 (as a release version value) and suffixed it with the actual Jenkins job's build number i.e. the last 4th digit - ex: set the name as: </p> <pre><code>${ENV,var="somepropertyvariable"}.${BUILD_NUMBER} </code></pre> <p>In this case, I'll start getting Jenkins builds as 2.75.0.1 to 2.75.0.x (where x is the last build# of that release (2.75.0)). Similarly, when I'll change the property release version to next i.e. 2.75.1 or 2.76.0, then the same Jenkins job will start giving me builds as 2.75.1.0, 2.75.1.1, ...., 2.75.1.x or 2.76.0.1, 2.76.0.2, ...., 2.76.0.x and so on. During the release version change, let say, our build will start from 1 again (as I mentioned above for 2.75.1 and 2.76.0 release versions).</p> <p>In this case, if my Jenkins job's build history (shows all builds for 2.75.0.x, 2.75.1.x and 2.76.0.x), then what change should I make in this script to include a 3rd parameter/argument. This 3rd argument will take release /version value i.e. either 2.75.0 or 2.75.1 or 2.76.0 and then this script should delete build numbers on that release only (and should NOT delete other release's builds).</p></li> </ol>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USArun Sangal
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODo not delete a Jenkins build if it's marked as "Keep this build forever" - Groovy script to delete Jenkins builds
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODo not delete a Jenkins build if it's marked as "Keep this build forever" - Groovy script to delete Jenkins builds
      1. USArun Sangal
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload