Skip to content
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

Merged
merged 1 commit into from
Jan 15, 2025
Merged

Reduce disk usage #1009

merged 1 commit into from
Jan 15, 2025

Conversation

fredg02
Copy link
Contributor

@fredg02 fredg02 commented Jan 15, 2025

This change should be applied to all branches and controllable forks.

This change should be applied to all branches and controllable forks.
@fredg02
Copy link
Contributor Author

fredg02 commented Jan 15, 2025

@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.

@jonahgraham
Copy link
Member

I will apply this to all branches and do the house keeping

@jonahgraham
Copy link
Member

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.

@jonahgraham jonahgraham merged commit e93588a into eclipse-cdt:main Jan 15, 2025
3 of 4 checks passed
jonahgraham pushed a commit to jonahgraham/cdt that referenced this pull request Jan 15, 2025
This change should be applied to all branches and controllable forks.
jonahgraham added a commit to jonahgraham/cdt that referenced this pull request Jan 15, 2025
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
jonahgraham added a commit to jonahgraham/cdt that referenced this pull request Jan 15, 2025
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
jonahgraham added a commit to jonahgraham/cdt that referenced this pull request Jan 15, 2025
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
jonahgraham added a commit to jonahgraham/cdt that referenced this pull request Jan 15, 2025
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
jonahgraham added a commit to jonahgraham/cdt that referenced this pull request Jan 15, 2025
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
jonahgraham added a commit to jonahgraham/cdt that referenced this pull request Jan 15, 2025
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
jonahgraham added a commit to jonahgraham/cdt that referenced this pull request Jan 15, 2025
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
jonahgraham added a commit to jonahgraham/cdt that referenced this pull request Jan 15, 2025
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
@fredg02
Copy link
Contributor Author

fredg02 commented Jan 15, 2025

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.

You can exclude branches in the job scm configuration.

@fredg02 fredg02 deleted the patch-1 branch January 15, 2025 15:50
@jonahgraham
Copy link
Member

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.

uses 90 GB of disk space at the moment.

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.

@jonahgraham
Copy link
Member

Please let me know current usage,

@fredg02 this was a question for you, forgot to tag you in above comment.

@fredg02
Copy link
Contributor Author

fredg02 commented Jan 15, 2025

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.

4.9 GB. This was a proper clean up! Thanks a lot.

@fredg02
Copy link
Contributor Author

fredg02 commented Jan 15, 2025

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.

@jonahgraham
Copy link
Member

I cancelled all the ongoing builds, they weren't doing anything particularly useful, go ahead and do the migration at your convenience.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants