[chore](github) BE UT workflows support branch checks#15147
Merged
morningman merged 1 commit intoapache:branch-1.2-ltsfrom Dec 17, 2022
Merged
[chore](github) BE UT workflows support branch checks#15147morningman merged 1 commit intoapache:branch-1.2-ltsfrom
morningman merged 1 commit intoapache:branch-1.2-ltsfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed changes
Issue Number: close #xxxProblem summary
Apache Doris made the branch
branch-1.2-ltsprotected. As a result, all pull requests for this branch should be checked before merging it.However, the BE UT workflows doesn't support branch checks and they fail to check the pull requests for the branch
branch-1.2-lts. The reason is that they download the wrong pre-built third-party libraries when they check the pull requests forbranch-1.2-lts. This PR resolves this issue.Checklist(Required)
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...