forked from opensearch-project/OpenSearch
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Compatibility with OpenSearch 2.17.1 #422
Labels
Comments
AlexRuiz7
added
level/task
Task issue
type/research
Research issue
request/operational
Operational requests
labels
Sep 20, 2024
1 task
AlexRuiz7
changed the title
Compatibility with OpenSearch 2.17.0
Compatibility with OpenSearch 2.17.1
Oct 18, 2024
3 tasks
OpenSearch and OpenSearch Dashboards 2.17.1 Release Notes
|
master~HEAD points to 98a6767 #!/bin/bash
export base="2.16.0"
export os_tag="2.17.1"
export from_branch="master"
export to_branch="${from_branch}-${os_tag}"
export pr_branch="migrate-${from_branch}-to-${os_tag}"
# Download latest changes from remotes
git fetch --all --tags
# Create temporal branches off the OpenSearch’s tag
git branch $to_branch refs/tags/$os_tag
git branch $pr_branch refs/tags/$os_tag
# Push the new branches to origin
git push -u origin $to_branch
git push -u origin $pr_branch
# ======= #
# Move to the working branch
git checkout $pr_branch
# Migrate the commits
git cherry-pick $base..$from_branch
# Check the number of commits before and after the migration is equal
previous=$(git rev-list $base..$from_branch --abbrev-commit | wc -l)
current=$(git rev-list $os_tag..$pr_branch --abbrev-commit | wc -l)
if [ "$current" -ne "$previous" ]
then
echo "Commits count before and after the migration are not equal. Migration failed!"
exit 1
fi |
4 tasks
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Description
We need to ensure the compatibility with the next version of OpenSearch v2.17.1.
This update is still being discussed, but we need to be aware of potential issues.
For that, we need to:
Issues
The text was updated successfully, but these errors were encountered: