Revert "ci: Add openEuler-cann in build/release"

[hipudding]

I found that the Release pipeline ran out of disk space due to the large size of the CANN backend’s container image. To avoid affecting the release of other tags, this PR was reverted.

Reverts #17192

[hipudding]

It’s possible that limiting the concurrency to 1 could resolve the disk space issue, and this approach is currently being verified.

[CISC]

Is it possible to use free-disk-space like in the docker releases?

[hipudding]

Is it possible to use free-disk-space like in the docker releases?

Do you mean deleting some caches when building the Docker image? We’ve already done that, but the container image is still quite large because the libraries required by CANN do take up a lot of disk space. Until we find a suitable solution, we should avoid blocking the release pipeline for now.

[CISC]

Is it possible to use free-disk-space like in the docker releases?

Do you mean deleting some caches when building the Docker image? We’ve already done that, but the container image is still quite large because the libraries required by CANN do take up a lot of disk space. Until we find a suitable solution, we should avoid blocking the release pipeline for now.

No, it deletes lots of stuff from the images, however it might be things you need (it does come with some options though).
https://github.com/ggml-org/free-disk-space

[hipudding]

Thanks. I will try this way.

[hipudding]

This PR is closed because #17361 can resolve this issue.