nzw921rx opened a new pull request, #12812:
URL: https://github.com/apache/seatunnel/pull/12812
### Purpose of this pull request
Add a local debugging switch to the E2E container discovery: when
`RUN_ONLY_ZETA=true` is set, `ContainerUtil#discoverTestContainers` returns
only the SeaTunnel (Zeta) containers, so an E2E suite can be verified locally
without starting the Flink/Spark containers.
The switch defaults to `false`, so the CI behaviour is unchanged.
### Does this PR introduce _any_ user-facing change?
No.
### How was this patch tested?
* `./mvnw spotless:apply -pl seatunnel-e2e/seatunnel-e2e-common`
* `./mvnw -q -pl seatunnel-e2e/seatunnel-e2e-common test-compile`
* Local run with `RUN_ONLY_ZETA=true` (transforms E2E suites): only the Zeta
container is discovered and started, the Flink/Spark containers are skipped.
### 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)
* [ ] 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
[plugin-mapping.properties](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)
3. Add ci label in
[label-scope-conf](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/)
5. Update connector
[plugin_config](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]
