Skip to content

[chore](regression) Enable branch-4.2 pull request CI routing - #67744

Open
hello-stephen wants to merge 1 commit into
masterfrom
ci/support-branch-4.2-teamcity
Open

[chore](regression) Enable branch-4.2 pull request CI routing#67744
hello-stephen wants to merge 1 commit into
masterfrom
ci/support-branch-4.2-teamcity

Conversation

@hello-stephen

Copy link
Copy Markdown
Contributor

What problem does this PR solve?

Issue Number: close #xxx

Related PR: None

Problem Summary: Pull requests targeting branch-4.2 are not mapped to the community TeamCity pipelines, and Vault P0 rejects branch-4.2 during preparation. Add the same pipeline matrix used by branch-4.1, excluding Performance and ARM, and allow Vault P0 preparation for branch-4.2.

Release note

None

Check List (For Author)

  • Test: Manual test
    • Validated shell syntax and the exact branch-4.2 pipeline mapping.
  • Behavior changed: Yes (pull requests targeting branch-4.2 are routed to the supported community CI matrix)
  • Does this need documentation: No

### What problem does this PR solve?

Issue Number: close #xxx

Related PR: None

Problem Summary: Pull requests targeting branch-4.2 are not mapped to the community TeamCity pipelines, and Vault P0 rejects branch-4.2 during preparation. Add the same pipeline matrix used by branch-4.1, excluding Performance and ARM, and allow Vault P0 preparation for branch-4.2.

### Release note

None

### Check List (For Author)

- Test: Manual test

    - Validated shell syntax and the exact branch-4.2 pipeline mapping.

- Behavior changed: Yes (pull requests targeting branch-4.2 are routed to the supported community CI matrix)

- Does this need documentation: No
@hello-stephen

Copy link
Copy Markdown
Contributor Author

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

hello-stephen added a commit that referenced this pull request Sep 9, 2026
### What problem does this PR solve?

Issue Number: close #xxx

Related PR: #67744

Problem Summary: Pull requests targeting branch-4.2 are not mapped to the community TeamCity pipelines, and Vault P0 rejects branch-4.2 during preparation. Add a branch-4.2-specific matrix aligned with branch-4.1, excluding Performance and ARM, and allow Vault P0 preparation for branch-4.2. Existing mappings in the branch-4.2 baseline remain unchanged.

### Release note

None

### Check List (For Author)

- Test: Manual test

    - Validated shell syntax and the exact branch-4.2 pipeline mapping.

- Behavior changed: Yes (pull requests targeting branch-4.2 are routed to the supported community CI matrix)

- Does this need documentation: No
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant