nzw921rx opened a new pull request, #11970:
URL: https://github.com/apache/seatunnel/pull/11970
### Purpose of this pull request
This PR follows up on #11963 and incorporates the review conclusions:
1. Remove the retry wrapper from the two Maven compilation steps. A retry
cannot reliably distinguish a temporary dependency-download failure from a
deterministic compilation failure introduced by the queued change, so the
original failure should be reported directly.
2. Configure the ASF Infra `apache/root` team as the emergency fallback for
the Merge Queue ruleset. This uses the same team ID as existing ASF
configurations and is intended only as a last-resort recovery path when the
queue remains unavailable after normal troubleshooting.
3. Add English and Chinese contributor guides covering:
* adding a PR to the queue;
* locating the corresponding `merge_group` workflow run;
* identifying the first useful Maven error;
* classifying compilation, infrastructure, timeout, and queue failures;
* recovering and requeueing a PR;
* handling a Merge Queue failure that cannot be recovered normally.
The Merge Queue ruleset remains separate from the existing classic branch
protection. The required pull-request `Build` and approval requirements
continue to be evaluated independently.
### Does this PR introduce *any* user-facing change?
Yes. It changes the repository-level Merge Queue recovery configuration for
the unreleased `dev` branch and adds contributor-facing operational
documentation.
It does not change SeaTunnel runtime behavior, public APIs, or released
versions.
### How was this patch tested?
The underlying Merge Queue build completed successfully in [[GitHub Actions
run
32937109261](https://github.com/apache/seatunnel/actions/runs/32937109261)](https://github.com/apache/seatunnel/actions/runs/32937109261).
The following configuration and documentation changes were also reviewed:
* The raw `bypass_actors` structure was compared with existing ASF
`.asf.yaml` configurations using the `apache/root` team.
* Removing the retry wrapper does not change either Maven command or its
arguments.
* The English and Chinese guides use the same structure and are registered
in the documentation sidebar.
* No runtime tests were added because this PR only changes repository CI
configuration and contributor documentation.
### Check list
* [ ] If any new Jar binary package adding in your PR, please add License
Notice according
[[New License
Guide](https://github.com/apache/seatunnel/blob/dev/docs/en/developer/new-license.md)](https://github.com/apache/seatunnel/blob/dev/docs/en/developer/new-license.md)
* [x] If necessary, please update the documentation to describe the new
feature. https://github.com/apache/seatunnel/tree/dev/docs
* [ ] If necessary, please update `incompatible-changes.md` to describe the
incompatibility caused by this PR.
* [ ] If you are contributing the connector code, please check that the
following files are updated:
1. Update
https://github.com/apache/seatunnel/blob/dev/plugin-mapping.properties and add
new connector information in it
2. Update the pom file of
[[seatunnel-dist](https://github.com/apache/seatunnel/blob/dev/seatunnel-dist/pom.xml)](https://github.com/apache/seatunnel/blob/dev/seatunnel-dist/pom.xml)
3. Add ci label in
[[label-scope-conf](https://github.com/apache/seatunnel/blob/dev/.github/workflows/labeler/label-scope-conf.yml)](https://github.com/apache/seatunnel/blob/dev/.github/workflows/labeler/label-scope-conf.yml)
4. Add e2e testcase in
[[seatunnel-e2e](https://github.com/apache/seatunnel/tree/dev/seatunnel-e2e/seatunnel-connector-v2-e2e/)](https://github.com/apache/seatunnel/tree/dev/seatunnel-e2e/seatunnel-connector-v2-e2e/)
5. Update connector
https://github.com/apache/seatunnel/blob/dev/config/plugin_config
--
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]
