...

2. How Checks are triggered?

All checks are automatically triggered when a Pull Request is submitted, or when the Pull Request is updated.

 1.The Checks 4,5,10,11 are triggered by TeamCity. The TeamCity service will detect the change of Doris Pull Request every 10 minutes and trigger the corresponding check(TeamCity Pipeline).

 2.The other Checks are triggered by Github Action. They will be triggered immediately after PR is submitted or updated.

Now we'll update the pipeline trigger on teamcity to include the following special keyword comments in the PULL REQUEST COMMENT section.

Key words:

        buildall: This keyword will trigger other pipelinings on teamcity other than external

        compile: This keyword will trigger the code compilation pipeline for the corresponding branch

        feut: This keyword will trigger the FE unit test pipeline

        beut: This keyword will trigger the BE unit test pipeline

        p0: This keyword will trigger the test pipeline for the P0 use case

        p1: This keyword will trigger the test pipeline for the P1 use case

        external: This keyword will trigger tests for the external component

Note:

        p0,p1, and external pipelining all depend on compile-phase output, so when you want to retry one of these pipelining separately, you need to make sure that the corresponding branch has compiled output. If not, please first run the compile phase by adding the keyword with compile in the comment area of the corresponding pull request. Build the dependency pipeline after compiling.

For example:

• When developers add a comment with a buildall keyword to the Conversation area of the PULL REQUEST, for example: "run buildall cases", git action will detect this behavior and trigger FE single test, BE single test, and code compilation pipeline. when the code compilation pipeline. p0 and p1 pipeline. if you want to execute data lake related use cases simultaneously, You can add external to buildall, and the external pipeline will automatically start the data lake environment to perform the relevant tests.

• When developers find a pipeline running error but want to retry it, they can add a comment with the pipeline keyword in the Conversation area of the PULL REQUEST, such as rerun p1. If p1 fails the test due to lack of compilation output, So we need to add a comment with the compile keyword first, and after successful compilation, p0,p1 pipeline will be automatically triggered.

3. How to View Checks

3.1 Github Action

...