ci: Move platform build checks from java binding to rust core

[Xuanwo]

No description provided.

[tisonkun]

We should verify build per PR which will be delivered in the release. Otherwise we should not release them or we "postpone" all the potential issues just before the release, which is not a good idea.

[Xuanwo]

We should verify build per PR which will be delivered in the release. Otherwise we should not release them or we "postpone" all the potential issues just before the release, which is not a good idea.

Service related staff should be covered by opendal rust core. So the real problem is we don't build opendal rust on all platforms. How about adding jobs to cover them instead so that we can aovid repeat those job at binding side?

TODO: move redis related tests to a separate job

I add this since I prefer to remove testcontainer in java binding. It's not scalable for neither bindings nor services. I'm seeking ways to integrate existing behavior tests with binding features so binding developers don't need to test services one by one.

[tisonkun]

Service related staff should be covered by opendal rust core. So the real problem is we don't build opendal rust on all platforms. How about adding jobs to cover them instead so that we can aovid repeat those job at binding side?

Make sense.

It's not scalable for neither bindings nor services.

I don't think we should "keep consistency" among bindings; each binding can have its own test suite for coverage. If there is a better solution, we can migrate. But if we don't find a possible way yet, let's keep it as is.

[Xuanwo]

If there is a better solution, we can migrate. But if we don't find a possible way yet, let's keep it as is.

LGTM.

[Xuanwo]

The TODO for redis has been removed. And I'm working on to make sure opendal rust covered on all platform.

[Xuanwo]

cc @tisonkun, would you like to take a look again, thanks!

[tisonkun]

Thank you! LGTM.