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

Fix release git url & document lessons learned #17677

Merged
merged 2 commits into from
Apr 2, 2024

Conversation

jmhbnz
Copy link
Member

@jmhbnz jmhbnz commented Mar 30, 2024

We recently released etcd v3.5.13. This pull request captures lessons from the release to ensure future releases can be smoother.

  1. Versions specified on the release script must not be prefixed.
  2. Git remote should be ssh format since pushing to github with https requires tokens now.
  3. Network timeouts can occur pushing images, but it is safe to re-run the script.
  4. Release script requires signing tags with gpg keys, ssh signing is not supported yet.

From 2021-08-13, GitHub is no longer accepting account passwords when authenticating Git operations. You need to add a PAT (Personal Access Token) instead for HTTPS. We should intead keep things simple and just use ssh to push to GitHub.

Signed-off-by: James Blair <[email protected]>
@@ -61,7 +61,7 @@ main() {
REPOSITORY=$(pwd)
BRANCH=$(git rev-parse --abbrev-ref HEAD)
else
REPOSITORY=${REPOSITORY:-"https://github.com/etcd-io/etcd.git"}
REPOSITORY=${REPOSITORY:-"git@github.com:etcd-io/etcd.git"}
Copy link
Member Author

Choose a reason for hiding this comment

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

If this change is accepted I will backport it to release-3.4 and release-3.5.

Copy link
Member

Choose a reason for hiding this comment

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

If this change is accepted I will backport it to release-3.4 and release-3.5.

It's OK to backport the change to release-3.5. But let's keep 3.4 as it's. I haven't seen any issues so far when releasing 3.4, we don't really want to any surprise.

Copy link
Member Author

Choose a reason for hiding this comment

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

Fair enough. We haven't seen the issue because we have been manually creating and pushing tag.

Copy link
Member

Choose a reason for hiding this comment

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

The scheme/protocol for cloning a repository can be a personal preference. If you have properly configured Git for HTTP authentication, it should work fine. You could potentially use GitHub without an SSH key.

That's why I think the scheme could be opinionated. Maybe a good middle ground would be to receive an option --use-https-repository-url (or --use-ssh-repository-url), to switch from https and ssh, and keep the release scripts more in sync... Or we could also leave it as-is, according to each release manager preference :)

@jmhbnz jmhbnz requested review from serathius and ahrtr March 30, 2024 21:30
Capturing lessons learned from etcd 3.5.13 release.

Signed-off-by: James Blair <[email protected]>
@jmhbnz jmhbnz force-pushed the fix-release-issues branch from 262ed59 to a9e4e2a Compare March 31, 2024 19:04
@jmhbnz
Copy link
Member Author

jmhbnz commented Mar 31, 2024

/retest

Flake already reported.

Copy link
Member

@ahrtr ahrtr left a comment

Choose a reason for hiding this comment

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

lgtm

Thanks

@ahrtr ahrtr merged commit a08812e into etcd-io:main Apr 2, 2024
39 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants