Yikun commented on pull request #35830: URL: https://github.com/apache/spark/pull/35830#issuecomment-1072465716
I think recent k8s ci breaks have proved that this CI is useful, it helps found 2 [[1]](https://github.com/apache/spark/pull/35839#issuecomment-1067982024) [[2]](https://github.com/apache/spark/pull/35504#issuecomment-1069843470) master bugs within 3 days, and also help some on regression test. I also contact with ASF, **minikube is allowed in Apache projects**, see: [INFRA-23000](https://issues.apache.org/jira/projects/INFRA/issues/INFRA-23000). For current implementations, we enable 3 style - **on push**: validation on each commits pushed and merged, use Apache repo resource. - **workflow_dispatch** for manually PR/Branch/tags validation, <img width="1277" alt="image" src="https://user-images.githubusercontent.com/1736354/159019635-fce4b8a0-3c8e-4d76-afad-f82e5bcf21ec.png"> Use distribution repo ci resource: ``` # Enable workflow_dispatch to help validate below case manually: # 1. Validate K8S IT for pull request: # spark-ref: refs/pull/35786/head # sync-current: true # 2. Validate K8S IT for specific SHA: # spark-ref: {Commit SHA} # sync-current: true # 3. Validate K8S IT for specific TAG/Branch using **master workflow**: # spark-ref: branch-3.3 or v3.3.0 # sync-current: false ``` 1. workflow_dispatch: [refs/pull/35786/head demo](https://github.com/Yikun/spark/runs/5598207912?check_suite_focus=true) 2. workflow_dispatch: [branch-3.3 demo](https://github.com/Yikun/spark/runs/5598210635?check_suite_focus=true) This is failed due to branch-3.3 haven't supprot test.driver.cpu yet, this also a good example to [show failed result upload](https://github.com/Yikun/spark/actions/runs/2003300365). 3. on push: [test demo](https://github.com/Yikun/spark/runs/5598194384?check_suite_focus=true) -- 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]
