refactor(record): merge the three image record loops into one script (#1541)
The app layer recorded its pushes with record_app_image_tag.py and the base and runtime layers with record_runtime_image.py, and the two had drifted: three copies of _git / _gh_api, two composite actions whose interpreter dance was byte-identical, and two of the three wheel-info copies.
One entry point now covers all three: scripts/record_image.py –layer {base,runtime,app}. What each layer commits is genuinely different (a changelog date for base/runtime; the status matrix image_tag plus a docs pipeline re-run for app), so the layer body stays separate and only the shared mechanics — the Harbor push_time query, the rebase-and-retry push onto a per-record branch, the review-gated PR — move into scripts/ record_common.py. gen_wheel_info.py imports the same module instead of carrying a third copy.
The two composite actions collapse into .github/actions/record-image/, which all five image workflows now use.
Co-authored-by: flagos-ci noreply@flagos.net
版权所有:中国计算机学会技术支持:开源发展技术委员会
京ICP备13000930号-9
京公网安备 11010802047560号
build-infra
FlagOS container image build infrastructure. This repo defines and builds the base images — a vendor’s SDK and toolchain on an OS base — that FlagOS runtime images are built on.
📖 Documentation: https://flagos-ai.github.io/release-info/
The docs (supported backends, per-image environment, dependencies) are generated from
configs.yaml+base/, so they can’t drift from the source.Layout
configs.yamlbase/<vendor>-<backend>scripts/build_base.pyscripts/generate_matrix.pyconfigs.yamlscripts/build_runtime.py.github/build-config.ymlruntime/packaging/flagtree/docs/Quick start
Build a base image locally:
In CI, base images are built on demand via the Base Image Build (manual) workflow (
workflow_dispatch) — pick a backend (orall) and whether to push.To add a vendor/backend, see the onboarding guide.