[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-248320-105":3,"detail-sidebar-cat-1-en-105":81,"doc-detail-248320-en":126},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":74,"head_meta":76,"extra_data":78,"updated_unix":80},105,"en","codearts-build-best-practices-issue-1-issue-01","CodeArts Build Best Practices - Issue 1 - Issue 01","","CodeArts Build Best Practices provides step-by-step guidance for automating software delivery workflows using CodeArts Build. It explains how to build Maven-based projects, package build outputs into container images via a Dockerfile, and push those images to Huawei SWR for reuse in later compilation or deployment. The document defines scenario requirements, prerequisites for SWR organization and CodeArts Repo permissions, and outlines build-task creation, configuration and execution, plus how to verify results through build logs and output files. It also includes additional practices for dependency generation, npm packaging, custom environments, and role-based permissions.",{"@graph":14,"@context":73},[15,34,56],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/template/","Template",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/template/presentations/","Presentations",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/template/codearts-build-best-practices-issue-1-issue-01/248320/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/codearts-build-best-practices-issue-1-issue-01/248320.png","ImageObject",442,249,{"name":42,"@type":43},"Aria Callaghan","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-10-22","2026-09-12",true,{"@type":52,"interactionType":53,"userInteractionCount":55},"InteractionCounter",{"@type":54},"ViewAction",11,{"@type":57,"mainEntity":58},"FAQPage",[59,65,69],{"name":60,"@type":61,"acceptedAnswer":62},"What is the main workflow described for CodeArts Build using a Maven project?","Question",{"text":63,"@type":64},"Create a Maven build in CodeArts Build, package the build outputs into a Docker container using a Dockerfile, then build the Docker image and push it to SWR so it can be reused for later compilation or deployment.","Answer",{"name":66,"@type":61,"acceptedAnswer":67},"What prerequisites are required before running the practice?",{"text":68,"@type":64},"The user must have an SWR organization named codeci_gray and permissions for CodeArts Repo.",{"name":70,"@type":61,"acceptedAnswer":71},"How can the build results be verified?",{"text":72,"@type":64},"Check the build logs and the generated result files to confirm the build outputs are correct.","https://schema.org",{"og:url":32,"og:type":75,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":77,"canonical":32},"index,follow",{"doc_id":79,"site_id":7},248320,1789245407,{"code":4,"msg":82,"data":83},"success",[84,87,92,97,102,107,112,117,122],{"id":55,"doc_module":22,"doc_module_name":25,"category_name":29,"show_sort_weight":85,"slug":86},90,"presentations",{"id":88,"doc_module":22,"doc_module_name":25,"category_name":89,"show_sort_weight":90,"slug":91},12,"Resumes",80,"resumes",{"id":93,"doc_module":22,"doc_module_name":25,"category_name":94,"show_sort_weight":95,"slug":96},14,"Invoices",70,"invoices",{"id":98,"doc_module":22,"doc_module_name":25,"category_name":99,"show_sort_weight":100,"slug":101},15,"Posters",60,"posters",{"id":103,"doc_module":22,"doc_module_name":25,"category_name":104,"show_sort_weight":105,"slug":106},16,"Social Media",50,"social-media",{"id":108,"doc_module":22,"doc_module_name":25,"category_name":109,"show_sort_weight":110,"slug":111},17,"Forms",40,"forms",{"id":113,"doc_module":22,"doc_module_name":25,"category_name":114,"show_sort_weight":115,"slug":116},18,"Letters",30,"letters",{"id":118,"doc_module":22,"doc_module_name":25,"category_name":119,"show_sort_weight":120,"slug":121},21,"Paper Templates",5,"papers-templates",{"id":123,"doc_module":22,"doc_module_name":25,"category_name":124,"show_sort_weight":4,"slug":125},158,"General","general-158",{"code":4,"msg":82,"data":127},{"doc_id":79,"user_id":128,"nickname":42,"user_avatar":129,"doc_module":22,"category_id":55,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":55,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":95,"language":135,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":136,"faqs":137,"seo_title":138,"seo_description":12,"update_tm":80,"read_time":139},962084926284,"https://ap-avatar.wpscdn.com/davatar_29158cc5080c5b710cf443261637dec0","CodeArts Build  \nBest Practices  \nIssue 01  \nDate 2026-07-29  \nHUAWEI TECHNOLOGIES CO., LTD.  \nCopyright © Huawei Technologies Co., Ltd. 2026. All rights reserved.  \nNo part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.  \nTrademarks and Permissions  \nand other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.  \nAll other trademarks and trade names mentioned in this document are the property of their respective holders.  \nNotice  \nThe purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided \"AS IS\" without warranties, guarantees or representations of any kind, either express or implied.  \nThe information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.  \nIssue 01 (2026-07-29) Copyright © Huawei Technologies Co., Ltd. i  \nSecurity Declaration  \nVulnerability  \nHuawei's regulations on product vulnerability management are subject to the Vul. Response Process. For details about this process, visit the following web page:  \n[https://www.huawei.com/en/psirt/vul-response-process](https://www.huawei.com/en/psirt/vul-response-process)  \nFor vulnerability information, enterprise customers can visit the following web page:  \n[https://securitybulletin.huawei.com/enterprise/en/security-advisory](https://securitybulletin.huawei.com/enterprise/en/security-advisory)  \nIssue 01 (2026-07-29) Copyright © Huawei Technologies Co., Ltd. ii  \nContents  \n1 Creating a Docker Image with a Maven Artifact and Pushing the Image to SWR (Built-in Executors, GUI)........................................................................................................... 1  \n2 Building with Maven and Uploading the Software Package to the Self-hosted Repo (Built-in Executors, GUI)................................................................................................. 7  \n3 Building with Maven to Generate a Private Dependency for Another Build (Builtin Executors, GUI)..................................................................................................................... 13  \n4 Building with npm and Uploading the Software Package to the Release Repo (Built-in Executors, GUI)......................................................................................................... 22  \n5 Building with Maven (Custom Executors, GUI)............................................................. 26  \n6 Building with Maven, Uploading the Software Package, and Pushing the Image to SWR (Built-in Executors, Code)........................................................................................ 33  \n7 Running a Multi-Task Maven Build Project (Built-in Executors, Code)................... 39  \n8 Building with Maven Based on Non-default Dependencies and Uploading the Software Package to a Self-Hosted Repo (Built-in Executors, GUI).............................45  \n9 Running a Build Task on a Custom Environment (Built-in Executors, GUI)........... 52  \n10 Configuring Role-based Permissions Before Using CodeArts Build........................ 60  \nIssue 01 (2026-07-29) Copyright © Huawei Technologies Co., Ltd. iii  \nCodeArts Build Best Practices  \n1 Creating a Docker Image with a Maven Artifact and Pushing the Image to SWR (Built-in Executors, GUI)  \n1 Creating a Docker Image with a Maven  \nArtifact and Pushing the Image to SWR  \n(Built-in Executors, GUI)  \nScenario  \nIn this practice, you use CodeArts Build to","cbCaig3n4iR8kURf","https://ap.wps.com/l/cbCaig3n4iR8kURf","pdf",3052451,"English","# Creating a Docker Image with a Maven Artifact and Pushing the Image to SWR\n## Scenario\n## Requirements\n## Procedure\n# Building with Maven and Uploading the Software Package to the Self-hosted Repo\n## Scenario\n## Requirements\n## Procedure\n# Building with Maven to Generate a Private Dependency for Another Build\n## Scenario\n## Requirements\n## Procedure\n# Building with npm and Uploading the Software Package to the Release Repo\n## Scenario\n## Requirements\n## Procedure\n# Building with Maven (Custom Executors, GUI)\n## Scenario\n## Requirements\n## Procedure\n# Building with Maven, Uploading the Software Package, and Pushing the Image to SWR\n## Scenario\n## Requirements\n## Procedure\n# Running a Multi-Task Maven Build Project\n## Scenario\n## Requirements\n## Procedure\n# Building with Maven Based on Non-default Dependencies and Uploading to a Self-Hosted Repo\n## Scenario\n## Requirements\n## Procedure\n# Running a Build Task on a Custom Environment\n## Scenario\n## Requirements\n## Procedure\n# Configuring Role-based Permissions Before Using CodeArts Build","[{\"question\":\"What is the main workflow described for CodeArts Build using a Maven project?\",\"answer\":\"Create a Maven build in CodeArts Build, package the build outputs into a Docker container using a Dockerfile, then build the Docker image and push it to SWR so it can be reused for later compilation or deployment.\"},{\"question\":\"What prerequisites are required before running the practice?\",\"answer\":\"The user must have an SWR organization named codeci_gray and permissions for CodeArts Repo.\"},{\"question\":\"How can the build results be verified?\",\"answer\":\"Check the build logs and the generated result files to confirm the build outputs are correct.\"}]","CodeArts Build Best Practices - Issue 1 - Issue 01 | PDF",25]