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

[3.4] Fix pipeline failure for release test #14210

Merged
merged 1 commit into from
Jul 12, 2022

Conversation

ahrtr
Copy link
Member

@ahrtr ahrtr commented Jul 11, 2022

@ahrtr ahrtr force-pushed the fix_release_script branch 7 times, most recently from d5a4ad7 to 5cda87d Compare July 12, 2022 00:29
@ahrtr ahrtr force-pushed the fix_release_script branch from 5cda87d to be0ce4f Compare July 12, 2022 00:32
@ahrtr
Copy link
Member Author

ahrtr commented Jul 12, 2022

The reason why the release pipeline fails on release-3.4 but succeeds on release-3.5 is we clone local directory instead of the remote repo in release-3.5, so we can still see the tag v3.5.99 after cloning the repo. I fixed it for 3.4 in this PR.

% (cd release && 'git' 'clone' '/tmp/etcd-release-3.5.99/etcd')

The failure for this PR is because the change (this PR) hasn't been merged into release-3.4 yet. Each time when running the release pipeline, it just clones the remote repo and run the test again release-3.4.

@serathius @spzala @ptabor So we need to merge this PR firstly. Please take a look. thx

@ahrtr ahrtr changed the title fix pipeline failure for release test [3.4] Fix pipeline failure for release test Jul 12, 2022
@ahrtr ahrtr merged commit 06561ae into etcd-io:release-3.4 Jul 12, 2022
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.

2 participants