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

Trigger release actions if tag matches new -rc.X prerelease tags #1827

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

jhiemstrawisc
Copy link
Member

Since we now plan to give release candidates tags suffixed with -rc.X, where X indicates the release candidate number, we also need to run the release actions for these tags.

The release.yaml action generates artifacts for our github repo and marks things as a pre-release, so we definitely want it to trigger on release candidate tags. The build-prod-container.yaml action creates our containers, and since these are used by integrations to test release candidates, we also need those too. It looks like the triggers for dev container builds will already match against release candidate tags (if I can mentally parse the regex) so we should be fine there.

Since we now plan to give release candidates tags suffixed with `-rc.X`,
where X indicates the release candidate number, we also need to run the
release actions for these tags.

The release.yaml action generates artifacts for our github repo and marks
things as a pre-release, so we definitely want it to trigger on release
candidate tags. The build-prod-container.yaml action creates our containers,
and since these are used by integrations to test release candidates, we also
need those too. It looks like the triggers for dev container builds will
already match against release candidate tags (if I can mentally parse the
regex) so we should be fine there.
@jhiemstrawisc
Copy link
Member Author

@CannonLock and @matyasselmeci, I assigned you both as reviewers because I'm probably missing some other things that need to be updated in Pelican to handle the new tag structure. If you think of anything, can you work on changes and commit them directly to this branch?

@jhiemstrawisc jhiemstrawisc linked an issue Dec 13, 2024 that may be closed by this pull request
@jhiemstrawisc jhiemstrawisc added the infrastructure GitHub Actions, Release management, and CI label Dec 13, 2024
@jhiemstrawisc jhiemstrawisc added this to the v7.12.0 milestone Dec 13, 2024
Copy link
Contributor

@matyasselmeci matyasselmeci left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't make a line comment for this because it's not in the lines you changed, but you should make sure that images for "rc" versions do not get tagged "latest". That should be around line 97 of build-prod-container.yml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure GitHub Actions, Release management, and CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Modify release process to handle -rc.X release candidate tags
2 participants