eye-gu opened a new issue, #7004: URL: https://github.com/apache/shenyu/issues/7004
### Describe the bug Since Aug 29, 2026, CI fails on **all** PRs at the environment-setup step (before any compilation), with the same error in every affected job: ``` curl -sL https://downloads.apache.org/maven/mvnd/1.0.2/maven-mvnd-1.0.2-linux-amd64.zip -o mvnd.zip unzip -q mvnd.zip End-of-central-directory signature not found. Either this file is not a zipfile... unzip: cannot find zipfile directory in one of mvnd.zip ##[error] Process completed with exit code 9 ``` ### Root cause The ASF download server keeps only the latest releases. `mvnd 1.0.2` has been removed from https://downloads.apache.org/maven/mvnd/ — the directory now only contains `1.0.6/` and `2.0.0-rc-3/`, and the 1.0.2 URL returns **404**. The workflows use `curl -sL` (without `-f`), so the 404 HTML page is saved as `mvnd.zip` and `unzip` fails with exit code 9. This is unrelated to any PR's code. Examples failing with identical logs: - #6347 (job log: https://github.com/apache/shenyu/actions/runs/33256032909/job/99109798425) - #7003 (job log: https://github.com/apache/shenyu/actions/runs/33264158565/job/99131122370) The last green run on master was Aug 26, which predates the artifact removal. ### Affected workflows All 7 workflow files on master that pin `MVND_VERSION=1.0.2`: `ci.yml`, `docker-publish.yml`, `docker-publish-dockerhub.yml`, `e2e-k8s.yml`, `integrated-test.yml`, `integrated-test-k8s-ingress.yml`, `k8s-examples-http.yml` ### Suggested fix 1. Bump `MVND_VERSION` from `1.0.2` to `1.0.6` (verified available, same artifact naming: `maven-mvnd-1.0.6-linux-amd64.zip` returns HTTP 200); or point to `https://archive.apache.org/dist/maven/mvnd/1.0.2/` which still hosts 1.0.2. 2. Add `-f` to the curl commands so download failures fail fast with a clear error instead of a corrupted zip. Happy to submit a PR for this if it helps. -- 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]
