hello-stephen opened a new pull request, #70450: URL: https://github.com/apache/doris/pull/70450
### Background Rootless CI consumes the regression configuration shipped with the tested PR. Older release-branch packages rely on deployment-time additions instead of the source-owned configuration introduced on master. ### What problem does this PR solve? Issue Number: None Related PR: #70407, #70444 (backports; #70444 head df9422d23284e9651daec71018c45b34e68b0b2f) PR Type: Build/CI/Chore Problem Summary: Bring the reviewed temporary exclusions and versioned CI configuration ownership to branch-4.1. Preserve the final Cloud S3 restoration from #70444 and the branch's existing suite/directory filters, defaults, and original load-suite initialization. ### Details - **Change map:** 14 pipeline configuration/documentation files; no production, framework, case-body, assertion or expected-result changes. - **Affected:** P0, CloudP0, VaultP0, NonConcurrent and External source profiles. The marker selects the deployed source-owned consumer. The rootless CI opt-in adds 82 P0, 24 CloudP0, 4 NonConcurrent and 3 External suite names to the branch's existing exclusions; VaultP0 adds none. The inherited name-only filter has the same documented outfile-name collisions as master. - **Developer and release impact:** Groovy settings are enabled only by `DORIS_CI_PRISTINE_FRAMEWORK=true`; port, Python venv and MetaService logging settings match #70444. Keep release-branch directory names and feature settings rather than copying whole master configurations. Two COS/OBS credential suites (`test_outfile_with_different_s3`, `test_file_tvf_s3`) are P2 on master but still P0 here, so explicitly exclude their names in P0/CloudP0 under the opt-in flag. Their original bodies unconditionally require independent provider credentials. These exclusions reduce coverage and do not establish that the cases are fixed. - **Behavior change:** CI selects the reviewed source-owned configuration, retaining the Cloud S3 suites restored by #70444. That master's targeted validation is not evidence of release-branch success. - **License and third-party:** No new dependencies or licenses. - **Rollback:** Remove the version marker to restore the deployed legacy configuration path; remove individual exclusions only after validating their prerequisites and original cases. ### Testing - Groovy 4.0.19 ConfigSlurper verification of all five profiles with the opt-in flag enabled and disabled: opt-out unchanged, source settings and exclusion deltas match master plus exactly the two branch-specific credential cases. - Verified all version-marker-required profile files exist and the diff is confined to the 14 expected pipeline files; `git diff --check` passes. - Full CI validation pending for Compile, FEUT, BEUT, CloudUT, P0, CloudP0, VaultP0 and NonConcurrent. External and Performance are outside this validation scope. Each PR/pipeline is limited to three total attempts, including subsequent heads; excluded lanes and cases are not reported as passing. ### Release note None. ### Check List (For Author) - Behavior changed: Yes (see Details). - Does this need documentation: No (included source configuration ownership note). - Pre-submission status: Partially verified: local configuration checks passed; full CI remains pending. ### AI Disclosure - Tool: OpenAI Codex. - Generated: Backport, branch-specific configuration adaptation, verification and PR description. - Human review: Pending maintainer review. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
