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

Cleaning up old CI jobs #440

Closed
fredg02 opened this issue Dec 9, 2024 · 6 comments
Closed

Cleaning up old CI jobs #440

fredg02 opened this issue Dec 9, 2024 · 6 comments
Assignees

Comments

@fredg02
Copy link

fredg02 commented Dec 9, 2024

Please consider cleaning up old CI jobs on the Linux Tools Jenkins instance.

For example, https://ci.eclipse.org/linuxtools/job/linuxtools/ shows branches that have not been built in more than a year. If you want to store build artifacts permanently, please store them on download.eclipse.org.

cc: @akurtakov

@akurtakov
Copy link
Contributor

They are there due to jenkinsfile in the branch. Is there an easier way than removing jenkinsfile from branches?

@fredg02
Copy link
Author

fredg02 commented Dec 10, 2024

You can exclude the branches in the branch sources configuration here: https://ci.eclipse.org/linuxtools/job/linuxtools/configure

Branches stable-8.6, stable-8.7, stable-8.8, stable-8.9 are only kept around since one of the builds is marked as keep forever.

@akurtakov
Copy link
Contributor

@jjohnstn Please stop marking builds "keep forever".

@akurtakov
Copy link
Contributor

Thanks for the guidance. Builds are no longer marked to keep for ever and jenkins did it cleanup. What's left is simply not garbage collected as there are no other builds to clean up. Please reopen with more details what I've missed if there is smth pending.

@akurtakov akurtakov self-assigned this Dec 10, 2024
@akurtakov akurtakov moved this to Done in Java Tooling Dec 10, 2024
@fredg02
Copy link
Author

fredg02 commented Dec 10, 2024

I've reduced Max # of old items to keep from 5 to 1 in the branch source config to remove the remaining branches that were not cleaned up. If a branch is excluded, it should actually be removed despite this setting. I'd consider this a bug in the Multi-branch source plugin.

@fredg02
Copy link
Author

fredg02 commented Dec 10, 2024

Thanks for cleaning up! 👍

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

No branches or pull requests

2 participants