linghengqian opened a new issue, #21051: URL: https://github.com/apache/shardingsphere/issues/21051
## Feature Request **For English only**, other languages will not accept. Please pay attention on issues you submitted, because we maybe need more details. If no response anymore and we cannot make decision by current information, we will **close it**. Please answer these questions before submitting your issue. Thanks! ### Is your feature request related to a problem? - Yes, this issue continues https://github.com/apache/shardingsphere/issues/19845 and https://github.com/apache/shardingsphere/issues/17451 for the issue of unit testing in GraalVM Native Image via JUnit Platform which the discussion content of . - For observing build errors of GraalVM Native Image, this issue is an extension of https://github.com/apache/shardingsphere/issues/17779 . - The target of this issue may be related to https://github.com/apache/shardingsphere/discussions/12594 . ### Describe the feature you would like. - According to GraalVM team members at https://twitter.com/fniephaus/status/1565419507346071552?t=B2SPn4OIVDpiGeIkzSrDVA&s=19 , `GraalVM 22.2` has been integrated with Github Action friendly, which means something like https://twitter.com/mraible/status/1498471457638293507?t=KFjwXLVc5QxTtCnTuTcIoQ&s=19 slow build mentioned by should be sufficiently mitigated. - Due to the launch of the https://github.com/oracle/graalvm-reachability-metadata repository, for the metadata-related json required for GraalVM builds, we no longer need to consider how to place the json tested in the environment in the master branch of ShardingSphere and how to place them that cannot be used in JDK8 CI. For files missing from the build, we can commit directly to https://github.com/oracle/graalvm-reachability-metadata . - Although considering the impact of Apache Calcite's dependencies with dynamic libraries, it is impossible to build the master branch of ShardingSphere directly using the `native-image` plugin of GraalVM, but I still think that setting up a nightly build in Github Action will help improve development of the user's test, and finally achieve the purpose of building a successful. After all, for regular developers, building GraalVM Native Image locally is very time-consuming, and devices with different operating systems behave differently. Joining a nightly build I think is a reasonable move. - The purpose of this issue is to provide a new specific `dockerfile` and `start.sh` and create a new cron timed CI job under https://github.com/apache/shardingsphere/tree/master/.github%2Fworkflows . At the same time the job must be allowed to fail. -- 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]
