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

chore: remove old staging/devspaces/build-requirements/devspaces-*-pluginregistry folders from spmm-util server once they're outdated #1039

Open
wants to merge 1 commit into
base: devspaces-3-rhel-8
Choose a base branch
from

Conversation

nickboldt
Copy link
Member

@nickboldt nickboldt commented Jan 8, 2024

What does this PR do?

chore: remove old staging/devspaces/build-requirements/devspaces-*-pluginregistry folders from spmm-util server once they're outdated

Change-Id: I09305e51700b04197ff4a636e36616320c6d8f70
Signed-off-by: RHDH Build (rhdh-bot) [email protected]

Screenshot/screencast of this PR

N/A

What issues does this PR fix or reference?

N/A (or see commit message above for issue number)

How to test this PR?

run the script using the new flag --delete-old-versions

check if https://download.devel.redhat.com/rcm-guest/staging/devspaces/build-requirements/devspaces-3.7-pluginregistry/ and https://download.devel.redhat.com/rcm-guest/staging/devspaces/build-requirements/devspaces-3.8-pluginregistry/ and https://download.devel.redhat.com/rcm-guest/staging/devspaces/build-requirements/devspaces-3.9-pluginregistry/ are deleted.

PR Checklist

As the author of this Pull Request I made sure that:

Reviewers

Reviewers, please comment how you tested the PR when approving it.

…uginregistry folders from spmm-util server once they're outdated

Change-Id: I09305e51700b04197ff4a636e36616320c6d8f70
Signed-off-by: RHDH Build (rhdh-bot) <[email protected]>
@nickboldt nickboldt changed the title chore: remove old... chore: remove old staging/devspaces/build-requirements/devspaces-*-pluginregistry folders from spmm-util server once they're outdated Jan 8, 2024
@nickboldt
Copy link
Member Author

If approved, will likely want to cherrypick this to 3.11 branch and also add the --delete-old-versions flag to Jenkins jobs where vsix files are created/published.

@nickboldt nickboldt requested a review from svor January 8, 2024 17:26
@SDawley
Copy link
Collaborator

SDawley commented Jan 8, 2024

On the one hand this is a good idea and we should actually start doing it once we have cachito builds running.
On the other we have not gotten a full build of all plugins since 3.9 so I am still using those plugins to test cachito.

@nickboldt
Copy link
Member Author

I am still using those plugins to test cachito.

That's why it's a new optional flag, rather than a default behaviour. I got your back. :D

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.

3 participants