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

[Refactor] Move the STARROCKS_VERSION and STARROCKS_COMMIT_HASH to the build.sh #24215

Merged
merged 1 commit into from
May 26, 2023

Conversation

chaoyli
Copy link
Contributor

@chaoyli chaoyli commented May 26, 2023

Currently, the two variables are defined in the build-support/gen_build_version.py. It's hard to debug and search. The pull request move the logic to the build.sh. The definition logic of STARROCKS_VERSION is as the following.

  1. If the user set the STARROCKS_VERSION, use the user's definition.
  2. If the current commit is a tag, use the tag name.
  3. If no tag is available, use the branch name
  4. If not a branch, use the commit-hash

What type of PR is this:

  • BugFix
  • Feature
  • Enhancement
  • Refactor
  • UT
  • Doc
  • Tool

Checklist:

  • I have added test cases for my bug fix or my new feature
  • This pr will affect users' behaviors
  • This pr needs user documentation (for new or modified features or behaviors)
    • I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

  • I have checked the version labels which the pr will be auto-backported to the target branch
    • 3.0
    • 2.5
    • 2.4
    • 2.3

…e build.sh

Currently, the two variable are defined in the build-support/gen_build_version.py.
It's hard to debug and search. The pull request move the logic to the build.sh.
The definition logic of STARROCKS_VERSION is as the following.
1. If the user set the STARROCKS_VERSION, use the user's definition.
2. If the current commit has a tag, use that tag
3. If no tag is available, use the branch name
4. If not a branch, use the commit-hash
@wanpengfei-git wanpengfei-git merged commit 5af915f into StarRocks:main May 26, 2023
@chaoyli
Copy link
Contributor Author

chaoyli commented Jun 2, 2023

@mergify backport branch-3.0

@mergify
Copy link
Contributor

mergify bot commented Jun 2, 2023

backport branch-3.0

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Jun 2, 2023
…e build.sh (#24215)

Currently, the two variables are defined in the
`build-support/gen_build_version.py`. It's hard to debug and search. The
pull request move the logic to the build.sh. The definition logic of
STARROCKS_VERSION is as the following.
1. If the user set the STARROCKS_VERSION, use the user's definition.
2. If the current commit is a tag, use the tag name.
3. If no tag is available, use the branch name
4. If not a branch, use the commit-hash

(cherry picked from commit 5af915f)

# Conflicts:
#	build-support/gen_build_version.py
#	build.sh
@chaoyli
Copy link
Contributor Author

chaoyli commented Jun 2, 2023

@mergify backport branch-2.5

@mergify
Copy link
Contributor

mergify bot commented Jun 2, 2023

backport branch-2.5

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Jun 2, 2023
…e build.sh (#24215)

Currently, the two variables are defined in the
`build-support/gen_build_version.py`. It's hard to debug and search. The
pull request move the logic to the build.sh. The definition logic of
STARROCKS_VERSION is as the following.
1. If the user set the STARROCKS_VERSION, use the user's definition.
2. If the current commit is a tag, use the tag name.
3. If no tag is available, use the branch name
4. If not a branch, use the commit-hash

(cherry picked from commit 5af915f)

# Conflicts:
#	build-support/gen_build_version.py
#	build.sh
abc982627271 pushed a commit to abc982627271/starrocks that referenced this pull request Jun 5, 2023
…e build.sh (StarRocks#24215)

Currently, the two variables are defined in the
`build-support/gen_build_version.py`. It's hard to debug and search. The
pull request move the logic to the build.sh. The definition logic of
STARROCKS_VERSION is as the following.
1. If the user set the STARROCKS_VERSION, use the user's definition.
2. If the current commit is a tag, use the tag name.
3. If no tag is available, use the branch name
4. If not a branch, use the commit-hash
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants