| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
ci: fix shell compatibility and simplify pipeline - Replace source with . for dash compatibility - Remove redundant summary and wait steps to prevent pipeline hanging - Clean up pipeline logic for better K8s reliability Signed-off-by: ycwang <wangyuchao12@huawei.com> | 3 个月前 | |
chore: consolidate sandbox post-merge fixes Preserve the original sandbox merge history while folding the follow-up CI, codecheck, packaging, deploy, and conflict-resolution commits into one merge commit. The tree is identical to the previous MR head 25a7b4e1fd7ea62d90e2e310a9b7414e4fb2d8a4. Signed-off-by: mhsong2 <songminhui2@huawei.com> | 1 个月前 | |
chore: consolidate sandbox packaging and CI fixes Signed-off-by: mhsong2 <songminhui2@huawei.com> | 22 天前 | |
chore: consolidate initial sandbox follow-up fixes Signed-off-by: mhsong2 <songminhui2@huawei.com> | 22 天前 | |
chore: consolidate sandbox post-merge fixes Preserve the original sandbox merge history while folding the follow-up CI, codecheck, packaging, deploy, and conflict-resolution commits into one merge commit. The tree is identical to the previous MR head 25a7b4e1fd7ea62d90e2e310a9b7414e4fb2d8a4. Signed-off-by: mhsong2 <songminhui2@huawei.com> | 1 个月前 | |
chore: consolidate sandbox runtime gate fixes Signed-off-by: mhsong2 <songminhui2@huawei.com> | 22 天前 | |
chore: consolidate sandbox packaging and CI fixes Signed-off-by: mhsong2 <songminhui2@huawei.com> | 22 天前 | |
chore: consolidate sandbox packaging and CI fixes Signed-off-by: mhsong2 <songminhui2@huawei.com> | 22 天前 | |
chore: consolidate sandbox runtime gate fixes Signed-off-by: mhsong2 <songminhui2@huawei.com> | 22 天前 | |
ci: run sandbox release through K8S smoke The webhook-triggered sandbox pipeline needed to exercise the full release path instead of stopping at package/image creation. This keeps macOS and arm builds enabled by default, builds the sandbox images from the packaged wheel runtime contents, deploys to the configured K8S target, and runs the off-cluster smoke suite after deployment. The squashed change also keeps the release path practical for repeated CI runs: K8S image/test steps download only the wheel artifacts they need, package assembly reuses staged trees, cache paths are reusable and aged, and smoke coverage is bounded so scheduler pressure does not turn the validation step into a long hang. Constraint: The K8S runtime launcher is now supplied by the openyuanrong wheel and deploy defaults, so the node image must not extract or pass a standalone runtime-launcher socket path. Constraint: Buildkite webhook runs need macOS and arm enabled by default while still publishing only the required release artifacts for downstream K8S work. Constraint: Test K8S deploys use the fixed kubeconfig path supplied by the agent-stack podSpec patch under yuanrong-ci chart ownership. Constraint: TestPyPI publishing must be limited to openyuanrong_sdk wheels and must read its token from a Kubernetes Secret, never from checked-in values. Rejected: Port the broader historical PR601 build-script refactor | it introduced more variables and churn than needed before this pipeline was green. Rejected: Keep the six-ref wait exception smoke | it tested scheduler pressure and hit the outer 600s timeout instead of proving wait exception semantics. Confidence: high Scope-risk: moderate Directive: Do not reintroduce standalone runtime-launcher extraction into the node image without first checking the wheel packaging and deploy/process launcher contract. Tested: Buildkite #323 passed on 4969d982d56a; Test K8S passed with 25 passed and 4 skipped in 190.59s; Build X86 + Build Image improved from 46m40s in #316 to 35m42s in #323. Tested: python3 -m py_compile test/st/python/test_off_cluster.py Tested: bash -n test/st/run_off_cluster_test.sh .buildkite/test_sandbox_k8s.sh deploy/sandbox/k8s/bin/start-node.sh deploy/sandbox/k8s/bin/supervisord-node-entrypoint.sh .buildkite/package_sandbox_release.sh deploy/sandbox/k8s/build-images.sh scripts/package_yuanrong.sh Tested: python3 -m unittest deploy.sandbox.k8s.tests.test_yr_k8s_layout Tested: helm template yuanrong-ci deploy/helm/yuanrong-ci with and without secrets.targetKubeconfig.create=true Tested: bash .buildkite/pipeline.dynamic.yml rendered Test K8S without kubeconfig secret injection and with .buildkite/test_sandbox_k8s.sh Tested: bash .buildkite/pipeline.dynamic.yml rendered release artifact collection from output/*.whl only, without datasystem/functionsystem source whl recopy. Tested: rendered dynamic pipeline uploads only artifacts/release/openyuanrong_sdk*.whl to https://test.pypi.org/legacy/ from Build X86 when TEST_PYPI_API_TOKEN is present. Not-tested: Local direct kubectl access to guiyang target cluster from this shell, which timed out on TLS handshake after the pipeline had already passed. Signed-off-by: YuchaoWang <wyc984872769@hotmail.com> Signed-off-by: yuchaow <wangyuchao12@huawei.com> | 2 个月前 | |
ci: Speed up SDK dependency reuse The arm SDK matrix spends most of its wall time before cached Bazel actions run: Buildkite #12 shows arm cp39 taking about 13 minutes, with roughly 4 minutes in runtime thirdparty preparation and additional external repository fetch cost despite remote cache being enabled. Persisting SDK-required inputs under the existing /mnt/paas build cache lets repeated SDK jobs reuse them without changing default step dependencies. Tag-triggered release builds also need their OBS artifacts under the release channel rather than the daily timestamp directory, so the upload commands switch to release/<version>/... when YR_RELEASE_TAG or BUILDKITE_TAG is present. Constraint: SDK steps still run independently, so the shared thirdparty directory is guarded with flock to avoid concurrent writes. Rejected: Make SDK steps depend on a single warmup job | that would change the parallel execution shape the pipeline currently relies on. Confidence: medium Scope-risk: narrow Tested: bash -n build.sh .buildkite/pipeline.dynamic.yml .buildkite/package_sandbox_release.sh .buildkite/prepare_sdk_thirdparty_cache.sh Tested: generated tag-triggered dynamic pipeline YAML and verified OBS upload channel/version arguments are emitted Tested: python3 -m pytest deploy/sandbox/k8s/tests/test_yr_k8s_layout.py test/tools/test_upload_build_artifact.py -q Tested: Buildkite openyuanrong/yuanrong-yuchaow#50 passed warm SDK-only validation; Build SDK arm cp39 completed in 2.6m Not-tested: full tag-triggered release pipeline after this OBS channel fix Signed-off-by: yuchaow <wangyuchao12@huawei.com> | 2 个月前 | |
fix(smoke): set YR_GATEWAY_ADDRESS for sandbox tunnel and stabilize reverse tunnel test Separate Traefik gateway (8888/web) from frontend API (18888) in K8S smoke, render enableEvent via Helm overlay instead of post-deploy patch, and verify reverse tunnel through the local proxy URL rather than flaky sandbox exec. Signed-off-by: mhsong2 <songminhui2@huawei.com> | 19 天前 | |
ci: Support tag release builds Tag pushes now flow through the GitCode webhook relay as release builds. The relay maps numeric and v-prefixed tags into BUILD_VERSION/YR_BUILD_VERSION, disables Buildkite Package uploads for tag releases, and enables TestPyPI publishing. Wheel publishing is centralized in a dedicated Buildkite step so all SDK wheels from linux amd64, linux arm64, and macOS arm64 are collected before upload. Constraint: Tag release wheels must use plain public versions such as 0.7.50 because PyPI rejects local versions with '+'. Rejected: Keep TestPyPI upload inside the x86 SDK step | it would miss arm64 and macOS wheels and duplicate release policy. Confidence: high Scope-risk: moderate Directive: Do not re-enable Buildkite Package uploads for tag releases unless the release target changes. Tested: python3 -m unittest deploy/helm/yuanrong-ci/tests/test_gitcode_webhook_relay.py -v Tested: python3 -m pytest deploy/sandbox/k8s/tests/test_yr_k8s_layout.py -q Tested: bash -n .buildkite/pipeline.dynamic.yml .buildkite/upload_buildkite_packages.sh .buildkite/upload_test_pypi_wheels.sh .buildkite/package_sandbox_manifest.sh .buildkite/package_sandbox_release.sh Tested: helm template yuanrong-ci deploy/helm/yuanrong-ci --set gitcodeWebhookRelay.enabled=true Not-tested: Real GitCode tag webhook and real TestPyPI upload were not triggered to avoid publishing a release version during local validation. Signed-off-by: yuchaow <wangyuchao12@huawei.com> | 2 个月前 | |
chore: consolidate sandbox post-merge fixes Preserve the original sandbox merge history while folding the follow-up CI, codecheck, packaging, deploy, and conflict-resolution commits into one merge commit. The tree is identical to the previous MR head 25a7b4e1fd7ea62d90e2e310a9b7414e4fb2d8a4. Signed-off-by: mhsong2 <songminhui2@huawei.com> | 1 个月前 | |
ci: Route release packages through explicit registries Release and daily package artifacts now go through explicit OBS or PyPI/TestPyPI paths so Buildkite artifact storage only carries the generated archive index. OBS links are percent-encoded before metadata is shared, downstream downloads normalize old unescaped links before fetching artifacts, and yrcli sandbox create/delete now fall back or complete based on visible sandbox state. K8S smoke deployment now carries the selected runtime manifest tags through Helm, keeps the default in-node Python runtime stable, restarts frontend after master rollout so the embedded frontend driver is registered against the current master state, and reuses the already-installed smoke wheels instead of creating a second uv venv. Constraint: OBS treats unescaped '+' in object URLs as an invalid public download path and returns 403. Constraint: K8S smoke cleanup can race with sandbox lifecycle and see an already-removed instance. Constraint: SDK sandbox create may return an invisible id or fail with invalid function when the cluster only supports frontend sandbox creation. Constraint: Frontend can start before master during a multi-workload rollout; master then marks the frontend driver exiting and ordinary yrlib invokes are canceled before readiness. Constraint: Buildkite smoke already installs the selected wheels into SMOKE_PYTHON before invoking run_off_cluster_test.sh. Rejected: Keep raw object paths in metadata | downstream package and runtime image steps fail when versions use local-version '+' separators. Rejected: Make smoke tests ignore sandbox delete failures | yrcli delete should be idempotent for an already-missing sandbox. Rejected: Trust SDK create ids without checking visibility | yrcli list/query/exec can then exercise a non-usable sandbox id. Rejected: Add rootfs to every Python service in services.yaml | normal yrlib cp39 invokes should continue using the in-node runtime path. Rejected: Let run_off_cluster_test.sh build a second uv venv in Buildkite smoke | duplicate dependency resolution caused a long Test K8S stall after the wheels were already installed. Confidence: high Scope-risk: moderate Tested: python3 api/python/yr/tests/test_cli_scripts.py -q Tested: python3 -m pytest test/tools/test_upload_build_artifact.py -q Tested: python3 -m pytest deploy/sandbox/k8s/tests/test_yr_k8s_layout.py -q Tested: bash -n .buildkite/test_sandbox_k8s.sh .buildkite/package_sandbox_manifest.sh deploy/sandbox/k8s/deploy.sh test/st/run_off_cluster_test.sh && git diff --check Tested: deploy/sandbox/k8s/deploy.sh against guiyang namespace yr with Buildkite #63 images Tested: docker run compile image + test/st/run_off_cluster_test.sh -a 1.95.217.192:8888 -- -m smoke -> 33 passed in 21.16s Tested: docker run compile image + preinstalled wheels + run_off_cluster_test.sh --no-uv-venv -k test_invoke_basic -> passed in 1.10s Signed-off-by: yuchaow <wangyuchao12@huawei.com> | 1 个月前 | |
chore: consolidate sandbox post-merge fixes Preserve the original sandbox merge history while folding the follow-up CI, codecheck, packaging, deploy, and conflict-resolution commits into one merge commit. The tree is identical to the previous MR head 25a7b4e1fd7ea62d90e2e310a9b7414e4fb2d8a4. Signed-off-by: mhsong2 <songminhui2@huawei.com> | 1 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 3 个月前 | ||
| 1 个月前 | ||
| 22 天前 | ||
| 22 天前 | ||
| 1 个月前 | ||
| 22 天前 | ||
| 22 天前 | ||
| 22 天前 | ||
| 22 天前 | ||
| 2 个月前 | ||
| 2 个月前 | ||
| 19 天前 | ||
| 2 个月前 | ||
| 1 个月前 | ||
| 1 个月前 | ||
| 1 个月前 |