[CI] Add aspeed-arm64 build target for AST2700 BMC platform#25963
[CI] Add aspeed-arm64 build target for AST2700 BMC platform#25963yxieca merged 3 commits intosonic-net:masterfrom
Conversation
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Gfrom2016
changed the title
There was a problem hiding this comment.
Pull request overview
Adds a new Azure Pipelines build job group so CI produces the Aspeed AST2700 (BMC) arm64 installer image (sonic-aspeed-arm64.bin) alongside existing arm64 targets.
Changes:
- Introduced a new
aspeed-arm64job group in theBuildstage. - Configured the job to run on the existing
sonicso1ES-arm64pool withPLATFORM_NAME=aspeedandPLATFORM_ARCH=arm64.
You can also share your feedback on Copilot code review. Take the survey.
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: zitingguo <[email protected]>
Signed-off-by: zitingguo <[email protected]>
BMC is a minimal embedded platform that does not need REST API. Remove DOCKER_RESTAPI from the dockers list and add it to DISABLED_PACKAGES_LOCAL to skip building the package entirely. Co-authored-by: Copilot <[email protected]> Signed-off-by: zitingguo <[email protected]>
Gfrom2016
force-pushed
the
add_aspeed_build_target
branch
from
80d0d57 to
b85f86d
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
| $(DOCKER_EVENTD) $(DOCKER_DASH_HA) $(DOCKER_STP) | ||
| $(DOCKER_EVENTD) $(DOCKER_DASH_HA) $(DOCKER_STP) \ | ||
| $(DOCKER_RESTAPI) | ||
|
|
There was a problem hiding this comment.
Minor issue: is this change still needed?
There was a problem hiding this comment.
Yes, this is still needed. The DISABLED_PACKAGES_LOCAL + filter-out prevents these docker images from being built at all — removing them from _DOCKERS only prevents inclusion in the final image, but they'd still be compiled, wasting CI time on the arm64 runner. This follows the same pattern used by Pensando and NVIDIA Bluefield platforms.
The `` line is a debug print showing which packages are filtered — happy to remove it if you prefer cleaner output.
|
/azpw ms_conflict |
1 similar comment
|
/azpw ms_conflict |
Why I did it
Add a new CI build target
aspeed-arm64to enable building SONiC images for the Aspeed AST2700 BMC platform (arm64).The Aspeed AST2700 platform support was added in PR #24898 but no CI build target existed to produce the
sonic-aspeed-arm64.binimage. This PR adds the pipeline definition so the aspeed image is built alongside other arm64 targets.Work item tracking
How I did it
Added a new build target entry
aspeed-arm64inazure-pipelines.ymlunder the arm64 build stage, specifyingPLATFORM_NAME: aspeedandPLATFORM_ARCH: arm64, using the existingsonicso1ES-arm64pool.How to verify it
aspeed-arm64pipeline job runs successfully and producessonic-aspeed-arm64.binTested branch (Please provide the tested image version)
SONiC-OS-master-25963.1055394-49231a76b(Build ID: 1055394)Which release branch to backport (provide reason below if selected)
Description for the changelog
Add
aspeed-arm64build target to CI pipeline for Aspeed AST2700 BMC platform image builds.Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)
Signed-off-by: zitingguo [email protected]