[Pipeline issue] build pipeline does not support to trigger check_coverage_fe by comment
- Dominant language
- Java
- Stars
- 15.9k
- Forks
- 3.9k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 520
Description
related pr #67480
not able to trigger rerun check_coverage_fe by comment
as I checked code I believe it's a miss in teamcity script `/regression-test/pipeline/common/teamcity-utils.sh`
```teamcity-utils.sh
# github中评论的要触发的流水线名字
# 到
# teamcity流水线实际的名称
# 的映射
# 新加流水线需要修改这里
declare -A comment_to_pipeline
comment_to_pipeline=(
['feut']='Doris_Doris_FeUt'
['beut']='Doris_DorisBeUt_BeUt'
['cloudut']='Doris_DorisCloudUt_CloudUt'
['compile']='Doris_DorisCompile_Compile'
['p0']='Doris_DorisRegression_P0Regression'
['p1']='Doris_DorisRegression_P1Regression'
['external']='Doris_External_Regression'
['performance']='Doris_DorisPerformance_Performance'
['cloud_p0']='Doris_DorisRegression_CloudP0'
['cloud_p1']='Doris_DorisCloudRegression_CloudP1'
['vault_p0']='Doris_DorisCloudRegression_VaultP0'
['nonConcurrent']='Doris_DorisRegression_NonConcurrentRegression'
['check_coverage']='Doris_Coverage_Merge_P0_UT'
)
# github中评论的要触发的流水线名字
# 到
# teamcity流水线返回结果给github的名称
# 的映射
# 新加流水线需要修改这里
declare -A conment_to_context
conment_to_context=(
['compile']='COMPILE (DORIS_COMPILE)'
['feut']='FE UT (Doris FE UT)'
['beut']='BE UT (Doris BE UT)'
['cloudut']='Cloud UT (Doris Cloud UT)'
['p0']='P0 Regression (Doris Regression)'
['p1']='P1 Regression (Doris Regression)'
['external']='External Regression (Doris External Regression)'
['performance']='performance (Doris Performance)'
['cloud_p0']='cloud_p0 (Doris Cloud Regression)'
['cloud_p1']='cloud_p1 (Doris Cloud Regression)'
['vault_p0']='vault_p0 (Doris Cloud Regression)'
['nonConcurrent']='NonConcurrent Regression (nonConcurrent)'
['check_coverage']='check_coverage (Coverage)'
)
```
Contributor guide
Research direction
Start in /regression-test/pipeline/common/teamcity-utils.sh and inspect the comment_to_pipeline and conment_to_context mappings. Compare the missing check_coverage_fe trigger with related PR #67480 and the existing check_coverage entry. Done means a GitHub comment can trigger check_coverage_fe and report the expected pipeline context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, shell
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 78/100