cloudbase-ai opened a new pull request, #7368: URL: https://github.com/apache/shenyu/pull/7368
### What changed Add `elasticsearch:8.2.3` to the existing Docker image pre-pull retry step in the integration-test workflow. The image is required by `shenyu-integrated-test-http/docker-compose.yml`. ### Why The latest CI run for PR #6528 failed after approximately 9.5 minutes in `Start docker compose`: ```text Head "https://registry-1.docker.io/v2/library/elasticsearch/manifests/8.2.3": Get "https://auth.docker.io/token?...": read: connection reset by peer ``` The workflow already retries the Docker images needed by the build, but Elasticsearch was first pulled by `docker compose up` after Maven, examples, and integrated tests had completed. A transient registry failure therefore discarded the entire job and forced a rerun. Pre-pulling Elasticsearch moves that network dependency before the long build and applies the existing retry policy. ### Expected effect - Successful-run wall clock should remain approximately unchanged because Compose reuses the local image. - Transient Docker Hub failures get up to four pull attempts instead of failing immediately. - Failed pulls happen before the long Maven build, reducing wasted time on unrecoverable registry outages. ### Verification - Workflow YAML parsed successfully. - The referenced Compose image version exactly matches `elasticsearch:8.2.3`. - `git diff --check` passed. - A temporary HTTP IT trigger will validate that the pre-pulled image is reused; the trigger commit will be removed from the final PR history afterward. -- 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]
