-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reduce disk usage #1009
Reduce disk usage #1009
Conversation
This change should be applied to all branches and controllable forks.
@jonahgraham side note: please consider cleaning up the CDT Jenkins instance. It contains many outdated jobs (older than 2 years) and uses 90 GB of disk space at the moment. |
I will apply this to all branches and do the house keeping |
What I want to do for the multi-branch pipeline is stop building/delete the old branches, but I don't see a good way to do that. The best workaround seems to be removing the Jenkinsfile, which I will do for all non-current branches. |
This change should be applied to all branches and controllable forks.
Jenkins doesn't have an obvious way of disabling builds and removing them for old branches and the best workaround I found was to simply remove the Jenkinsfile See eclipse-cdt#1009
Jenkins doesn't have an obvious way of disabling builds and removing them for old branches and the best workaround I found was to simply remove the Jenkinsfile See eclipse-cdt#1009
Jenkins doesn't have an obvious way of disabling builds and removing them for old branches and the best workaround I found was to simply remove the Jenkinsfile See eclipse-cdt#1009
Jenkins doesn't have an obvious way of disabling builds and removing them for old branches and the best workaround I found was to simply remove the Jenkinsfile See eclipse-cdt#1009
Jenkins doesn't have an obvious way of disabling builds and removing them for old branches and the best workaround I found was to simply remove the Jenkinsfile See eclipse-cdt#1009
Jenkins doesn't have an obvious way of disabling builds and removing them for old branches and the best workaround I found was to simply remove the Jenkinsfile See eclipse-cdt#1009
Jenkins doesn't have an obvious way of disabling builds and removing them for old branches and the best workaround I found was to simply remove the Jenkinsfile See eclipse-cdt#1009
Jenkins doesn't have an obvious way of disabling builds and removing them for old branches and the best workaround I found was to simply remove the Jenkinsfile See eclipse-cdt#1009
You can exclude branches in the job scm configuration. |
Thanks for the advice - next time I need to disable a branch I will try that.
Please let me know current usage, AFAIK the disk usage plug-in is no longer available so I can't check myself. I hope it is vastly smaller as I deleted nearly everything except the very recent stuff. |
@fredg02 this was a question for you, forgot to tag you in above comment. |
4.9 GB. This was a proper clean up! Thanks a lot. |
Just a heads-up, once the current builds are finished, I will migrate the CDT JIPP to our new backend storage device. The JIPP will be offline for ~30 mins. |
I cancelled all the ongoing builds, they weren't doing anything particularly useful, go ahead and do the migration at your convenience. |
This change should be applied to all branches and controllable forks.