diff --git a/sig/ci-portal/OWNERS b/sig/ci-portal/OWNERS new file mode 100644 index 0000000000000000000000000000000000000000..b416c7dd570b560f85f3b8cdbab07ab626912475 --- /dev/null +++ b/sig/ci-portal/OWNERS @@ -0,0 +1,20 @@ +{ + "maintainers":[ + { + "gitee_id":"niuyuan888", + "gitee_email":"niuyuan@huawei.com" + }, + { + "gitee_id":"freet15", + "gitee_email":"zhaozhi@openatom.org" + }, + { + "gitee_id":"xzmu", + "gitee_email":"kelei@iscas.ac.cn" + }, + { + "gitee_id":"pityonline", + "gitee_email":"pityonline@gmail.com>" + }, + ] +} diff --git a/sig/ci-portal/sig_ci_portal.md b/sig/ci-portal/sig_ci_portal.md new file mode 100644 index 0000000000000000000000000000000000000000..aede3a23017097b27731111cf3463529a1017552 --- /dev/null +++ b/sig/ci-portal/sig_ci_portal.md @@ -0,0 +1,55 @@ +# CI Portal + +English | [简体中文](./sig_ci_portal_cn.md) + +Note: The content of this SIG follows the convention described in OpenHarmony's PMC Management Charter [README](/zh/pmc.md). + +## SIG group work objectives and scope + +OpenHarmony adopts the Continuous Integration (CI) to finds code problems in time, ensure reliable code quality and stable function. + +- Daily build: OpenHarmony's continuous integration pipeline is executed automatically every day, so as to find problems in static check, compilation and function of code in advance, fix problems in time, and ensure code quality. +- Access control build: After the developer submits the code merge request, the access control build will be triggered, such as static check, code compilation, function test, etc. only after the access control passes, can the code be merged. + +In order to facilitate developers to timely view and analyze the execution results of daily build and code access control build, it is necessary to provide a continuous integration portal (CI portal). + +### Work goals + +It provides a continuous integration portal for developers to view the status and results of OpenHarmony daily build and access control build. + +### The scope of work + +- Comb OpenHarmony code repositories, pipeline configuration and other basic information. +- Develop the integration scheme with code repositories and pipeline. +- Develop frontend page and backend service, display pipeline status, provide the preview and download of the pipeline log, binary file. +- Deployment of continuous integration portal can support 100 concurrent access. + +### The repository and description of the SIG management + +The continuous integration portal is separated as the frontend and the back end. The front end is based on [Vue](https://cn.vuejs.org/), and the backend micro service is based on [ServiceComb](http://servicecomb.apache.org/), divided into two code repositories. + +- Front page: [ci-portal-website](https://gitee.com/OpenHarmony-sig/ci-portal-website) +- Backend micro service: [ci-portal-service](https://gitee.com/OpenHarmony-sig/ci-portal-service ) + +## SIG Related Information + +### Maintainers + +- Niu Yuan [@niuyuan888](https://gitee.com/niuyuan888)] +- Ben [@freet15](https://gitee.com/freet15)] +- Liang Kelei [@xzmu](https://gitee.com/xzmu)] +- Leon [@pityonline](https://gitee.com/pityonline)] + +### Mailing Lists + +- dev@OpenHarmony.io + +### Slack group + +- +- The link to join the Slack group will be regularly updated in [OpenHarmony Community Code Warehouse](https://gitee.com/OpenHarmony/community) + +### Meeting + +- Meeting time: Monthly regular meeting, 14:15-15:15 pm on the second Wednesday of each month (UTC + 8) +- Conference link: Sent by email before meeting diff --git a/sig/ci-portal/sig_ci_portal_cn.md b/sig/ci-portal/sig_ci_portal_cn.md new file mode 100644 index 0000000000000000000000000000000000000000..54ae8323f63ddc5af4cca7766e6ac7704951ed1c --- /dev/null +++ b/sig/ci-portal/sig_ci_portal_cn.md @@ -0,0 +1,55 @@ +# CI门户 + +简体中文 | [English](./sig_ci_portal.md) + +说明：本SIG的内容遵循OpenHarmony的PMC管理章程 [README](/zh/pmc.md)中描述的约定。 + +## SIG组工作目标和范围 + +OpenHarmony通过持续集成（CI，Continuous Integration）及时发现代码问题，确保代码质量可靠和功能稳定： + +- 每日构建：OpenHarmony的持续集成流水线每日自动执行，以便提前发现代码静态检查、编译、功能等方面的问题，及时修复问题，确保代码质量。 +- 门禁构建：开发者向OpenHarmony提交代码合入申请后，会触发门禁检查，例如静态检查、代码编译、功能测试等，门禁通过后才能合入代码。 + +为了便于开发者及时查看、分析每日构建和代码门禁的执行结果，需要提供一个持续集成的门户（CI Portal）。 + +### 工作目标 + +提供一个持续集成门户，开发者可以查看OpenHarmony每日构建和门禁构建的状态和结果。 + +### 工作范围 + +- 梳理OpenHarmony代码仓、流水线配置等基础信息。 +- 制定与代码仓、流水线的集成对接方案。 +- 开发前台页面和后台服务，显示流水线状态，提供流水线日志、二进制文件的查看和下载。 +- 部署持续集成门户，能够支持100并发访问。 + +### Repository及描述 + +持续集成门户采用前后端分离的方式进行开发，前台基于[Vue](https://cn.vuejs.org/)，后台微服务基于[ServiceComb](http://servicecomb.apache.org/)，分为两个代码仓。 + +- 前台页面：[ci-portal-website](https://gitee.com/OpenHarmony-sig/ci-portal-website) +- 后台微服务：[ci-portal-service](https://gitee.com/OpenHarmony-sig/ci-portal-service) + +## SIG 相关信息 + +### Maintainers + +- Niu Yuan [@niuyuan888](https://gitee.com/niuyuan888)] +- Ben [@freet15](https://gitee.com/freet15)] +- Liang Kelei [@xzmu](https://gitee.com/xzmu)] +- Leon [@pityonline](https://gitee.com/pityonline)] + +### 邮件列表 + +- dev@OpenHarmony.io + +### Slack 群组 + +- +- 加入 Slack 群组的链接将定期更新在 [OpenHarmony Community代码仓](https://gitee.com/OpenHarmony/community) + +### 会议 + +- 会议时间：月例会，每月第二个周三下午14:15~15:15(UTC+8) +- 会议链接：会议前邮件发送会议链接 diff --git a/sig/sigs.json b/sig/sigs.json index 15e837b559c1e0f169d9d87c2116237e320e90ff..70bfdf4fd74f856f9bc99bd19a39e3c3f1d2ebff 100644 --- a/sig/sigs.json +++ b/sig/sigs.json @@ -10,5 +10,10 @@ "project-name":"https://gitee.com/openharmony-sig/updates", "project-path":"base/updates/" }, + { + "sig-name ":"ci-portal", + "project-name":"https://gitee.com/openharmony-sig/ci-portal", + "project-path": "none" + } ] }