[CI] Add no_proxy configuration for docker execution

[EmmonsCurse]

Motivation

CI tasks are affected by network instability when accessing internal services and third-party package mirrors through the proxy. This may lead to failures during dependency installation (e.g., pip install, wget), especially for domains that should be accessed directly.

To improve reliability and avoid unnecessary proxy routing, it is necessary to explicitly configure no_proxy for commonly used internal domains and mirror sources.

Modifications

• Added no_proxy environment variable in docker execution.
• Included internal domains and mirror sources (e.g., .bcebos.com, .baidu.com, .tuna.tsinghua.edu.cn, etc.) to bypass proxy.
• Ensured container network requests to these domains are directly connected instead of going through proxy, improving CI stability.

Usage or Command

N/A

Accuracy Tests

N/A

Checklist

• Add at least a tag in the PR title.
  • Tag list: [[FDConfig],[APIServer],[Engine], [Scheduler], [PD Disaggregation], [Executor], [Graph Optimization], [Speculative Decoding], [RL], [Models], [Quantization], [Loader], [OP], [KVCache], [DataProcessor], [BugFix], [Docs], [CI], [Optimization], [Feature], [Benchmark], [Others], [XPU], [HPU], [GCU], [DCU], [Iluvatar], [Metax]]
  • You can add new tags based on the PR content, but the semantics must be clear.
• Format your code, run pre-commit before commit.
• Add unit tests. Please write the reason in this PR if no unit tests.
• Provide accuracy results.
• If the current PR is submitting to the release branch, make sure the PR has been submitted to the develop branch, then cherry-pick it to the release branch with the [Cherry-Pick] PR tag.

[EmmonsCurse]

/skip-ci ci_iluvatar
/skip-ci ci_hpu
/skip-ci build_xpu
/skip-ci coverage
/skip-ci base_test
/skip-ci stable_test
/skip-ci gpu_4cards_test

[paddle-bot]

Thanks for your contribution!

[fastdeploy-bot]

🤖 AI Code Review | 2026-04-09 17:23 CST

📋 Review 摘要

PR 概述：为 14 个 CI workflow 文件添加统一的 no_proxy 环境变量配置，避免内部服务和镜像源通过代理访问
变更范围：.github/workflows/ 目录下的 CI 配置文件
影响面 Tag：CI

问题

级别	文件	概述
🟡 建议	多个文件	存在遗漏的 XPU/HPU 相关 workflow 文件，其 no_proxy 配置与本次 PR 不一致
🟡 建议	全局	相同的 no_proxy 字符串在 14 个文件中重复，后续维护成本较高

总体评价

本次变更意图清晰，通过配置 no_proxy 提高 CI 稳定性是合理的。但建议同步更新以下遗漏的文件以保持一致性：

• _build_xpu.yml
• _xpu_4cards_case_test.yml
• _xpu_8cards_case_test.yml
• ci_hpu.yml

这些文件中已有旧的 no_proxy 配置（值较短），建议一并更新为本次 PR 中的完整列表。

[fastdeploy-bot]

🟡 建议 发现以下 workflow 文件未被本次 PR 覆盖，但已有旧的 no_proxy 配置，建议同步更新以保持一致性：

文件	当前值
_build_xpu.yml:130	bcebos.com,mirrors.tuna.tsinghua.edu.cn,127.0.0.1,localhost
_xpu_4cards_case_test.yml:137	同上
_xpu_8cards_case_test.yml:132	同上
ci_hpu.yml:86	bcebos.com,mirrors.tuna.tsinghua.edu.cn,localhost,127.0.0.1,0.0.0.0,10.0.0.0/8,192.168.1.0/24

建议将这些文件的 no_proxy 值也更新为本次 PR 中的完整列表，确保所有 CI 任务行为一致。