Migrate workflow to delete old Cloudsmith artifacts to GitHub Actions #32146
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…creds, using builtin docker funcitonality in GA
|
@bjormel Could you look at this test run and verify that it deleted what it should and no more: I haven't changed the core logic so should be ok but just in case. |
esolitos
requested changes
Aug 14, 2024
esolitos
approved these changes
Aug 14, 2024
esolitos
changed the title
esolitos
deleted the
glebashink/gh-action-delete-old-versions-in-archive
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.
What
Adds a GitHub action workflow to delete old Cloudsmith artifacts.
The workflow is triggered either manually or on a daily schedule.
Why
Part of the process of retiring Screwdriver as CI/CD runner.
Additional Info
The corresponding Screwdriver pipeline is not removed since we don't have a dashboard for Github Actions yet.
See successful test run:
https://github.com/vespa-engine/vespa/actions/runs/10387039260/job/28759628746