hello-stephen opened a new pull request, #70444: URL: https://github.com/apache/doris/pull/70444
### Background The rootless CI deployment adapters currently append fixed settings and temporary suite exclusions after copying a profile from the cases package. This splits the effective configuration between this repository and the CI server. The regression framework itself remains unmodified. ### What problem does this PR solve? Issue Number: None Related PR: #70407 (earlier source-owned compatibility exclusions) PR Type: Build/CI/Chore Problem Summary: Move the remaining fixed configuration into the existing files under `regression-test/pipeline/`, with reasons beside the settings and exclusions. Add the 53 Cloud exclusion names that were still present only in the adapter; P0 and NonConcurrent already contain their adapter exclusions and receive no duplicated names. A small cases capability marker allows compatible deployment adapters to retain the complete legacy path for older packages. ### Details - **Affected:** P0, CloudP0, VaultP0, External and NonConcurrent pipeline configuration. FE ports are kept beside the existing FE settings; cloud Python mode and MetaService conflict-key logging are kept in their existing custom files. Fixed regression settings retain the existing pristine-framework opt-in. - **Developer and release impact:** Master only. Runtime addresses, directories, interpreter path/version, build IDs and temporary credentials remain deployment inputs. No framework, suite, assertion or expected-result edits. Branch-4.1, branch-4.2 and older master cases must continue to use the legacy adapter when the marker is absent. - **License and third-party:** No dependencies or licenses added. - **Rollback:** An older cases package lacks the capability marker and selects the retained legacy adapter. Reverting this PR does not require removing compatibility support from the deployment consumer. ### Testing Locally executed the current five deployment adapters against base configuration and the staged compatible adapter against this change. Parsed the generated regression files with Groovy ConfigSlurper and compared all effective settings and unique exclusion names; compared effective FE/BE/MS/recycler settings. All five profiles matched. Regression configuration with the opt-in disabled matched the base for all five profiles. Missing-marker fallback and unknown-version/incomplete-package rejection checks passed. Also exercised the old External adapter against the new source: it rejects `s3FixtureProtocol` as an unexpected source override, confirming the rollout dependency below. `git diff --check` passed. No full build or end-to-end cluster regression was run for this configuration-only change. ### Notes for Reviewers **Deployment prerequisite:** the compatible CI consumer is prepared separately and has not been deployed. Deploy the marker-aware entrypoint, retaining the original legacy modules, before consuming cases built from this PR. In particular, the current External adapter asserts that several settings are absent from source and cannot consume the new configuration directly. This source PR alone does not remove online script additions. See `regression-test/pipeline/CI_CONFIG.md` for the version-1 contract and rollout order. ### Release note None ### Check List (For Author) - Behavior changed: No (effective rootless configuration and suite selection are preserved with the compatible consumer) - Does this need documentation: No (CI ownership and rollout contract are documented in this repository) - Pre-submission status: Partially verified: local configuration equivalence passed; compatible consumer deployment and full runtime validation remain pending. ### AI Disclosure - Tool: OpenAI Codex - Generated: Configuration migration, local validation harness, compatibility consumer candidate, documentation and this 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]
