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

Add a helper script for releasing trustee #373

Merged

Conversation

portersrc
Copy link
Member

This is a bash script to help trustee maintainers perform releases. As the release guide changes, this script can/should change along with it.

This work follows from discussions for trustee's release process, e.g. see here. It is also similar in spirit to the one in peer pods here.

Example usage:

$ ./release-helper.sh -u GH_USERNAME -k GH_TOKEN -c latest -n v0.8.2

@portersrc portersrc requested a review from sameo as a code owner April 22, 2024 19:48
Copy link
Member

@Xynnn007 Xynnn007 left a comment

Choose a reason for hiding this comment

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

Cool PR! Thanks @portersrc I am ok with the image push parts.

cc @surajssd

@portersrc portersrc force-pushed the trustee-helper-release-script branch 2 times, most recently from a8c2f94 to 49912e1 Compare April 23, 2024 10:48
Copy link
Member

@fitzthum fitzthum left a comment

Choose a reason for hiding this comment

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

Looks good. Just one comment.

echo " -k A github token with permissions on trustee to write packages"
echo " and open PRs."
echo " -c This is the tag that's been tested and that you're happy with."
echo " You want to release from this tag. Example: latest"
Copy link
Member

Choose a reason for hiding this comment

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

Does it have to be a tag or could it be a commit sha?

Copy link
Member Author

Choose a reason for hiding this comment

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

Oh 🤔 good point. Ultimately the candidate-release-tag is used like so:

docker pull ${ghcr_repo}/${staged_pkg_name}:${candidate_release_tag}

E.g. for kbs:

docker pull ghcr.io/confidential-containers/staged-images/kbs:dc01f454264fb4350e5f69eba05683a9a1882c41

So it must be a tag for a GHCR package, but because we use commit shas for tagging our packages -- well -- a commit sha can be used. Let me update to make it clearer.

Copy link
Member Author

Choose a reason for hiding this comment

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

Ok, adopted your language suggestion here b/c it's better, I think. Thanks!

@portersrc portersrc force-pushed the trustee-helper-release-script branch from 49912e1 to 2a414e3 Compare April 24, 2024 13:51
Copy link
Member

@fitzthum fitzthum left a comment

Choose a reason for hiding this comment

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

LGTM. I guess we'll see how it works next release.

@fitzthum fitzthum merged commit 9753da4 into confidential-containers:main Apr 24, 2024
14 checks passed
@portersrc portersrc deleted the trustee-helper-release-script branch May 24, 2024 17:42
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