You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@doris.apache.org by stephen <he...@qq.com.INVALID> on 2022/04/25 08:33:06 UTC
回复：[DISCUSS] Add requested CI check for Pull Requests
+1
------------------ 原始邮件 ------------------
发件人: "dev" <morningman@163.com>;
发送时间: 2022年4月25日(星期一) 下午4:17
收件人: "dev"<dev@doris.apache.org>;
主题: Re:[DISCUSS] Add requested CI check for Pull Requests
+1
--
此致！Best Regards
陈明雨 Mingyu Chen
Email:
chenmingyu@apache.org
At 2022-04-25 16:13:20, "GuoLei Yi" <yiguolei@gmail.com> wrote:
>Hello everyone, with the increasing number of pull requests, we need to
>strictly control the code merge process. I plan to turn on "requested" CI
>checks, that is, when all "requested" CI checks of a PR pass, the code can
>be merged. The following admissions will be forced on: 1. BE Code Formatter
>/ Clang Formatter (pull_request): Code formatter for BE. 2. Build
>Extensions / Build Extensions (pull_request): Compile for fs_broker/doc/. 3.
>License Check / License Check (pull_request): License Header check. 4. BE
>UT (Doris BE UT): Run BE unit test. 5. FE UT (Doris FE UT): Run FE unit
>test. 6. P0 regression (Doris P0 regression): Compile FE/BE and run
>regression test. PPMC members are obliged to manage the above CI
>checks. Welcome
>to discuss this, after unanimous agreement, I will apply to ASF Infra to
>open requested CI.
>--
>祝您心情愉快
>
>衣国垒
>Tsing Hua University
>Tel:134-3991-0228
>Email:yiguolei@gmail.com