Currently we are locking the Release build numbers to keep it forever without getting deleted, but the issue here is each build size is around 3 to 5 GB. So overall release branches will have more than 50 builds.
Which is our bigger concern that it is occupying more space, as result we are facing slowness in jenkins loading or getting struck often.
Below is our product structure.
<component1>
<component2>
<component3>
<component4>
toolkit
Every branch will have all the above components, we are having separate jenkins jobs for every component.
and finally we run toolkit build in jenkins once all other components were build properly and pushed the artifacts to jfrog.
Toolkit-CI will pack the rpm's based on the script we have written. while packing it will download depandant jar, war and sar files from Jfrog.
We are having separate Release build, which people will trigger once the toolkit passed successfully.
Here one method we decided is tagging the current commits in every component when the RB is getting triggered.
So that we can delete the RB, in future if we need that particular RB, by the tag name (which will be there in every component) we can recreate the RB.
So jenkins disk space will not be occupied by Release builds.
If there is any other suggestions or any efficient methodoloy you are using in your org pls drop here.