We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
T_PIPELINE_WEBHOOK 记录代码仓库与流水线的绑定关系,表结构如下:
PROJECT_NAME 通过仓库名获取,这么写是因为工蜂svn触发时,仓库名为三层时,只需要取中间一层
fun getProjectName(projectName: String): String { // 如果项目名是三层的,比如a/b/c,那对应的rep_name是b val repoSplit = projectName.split("/") if (repoSplit.size != 3) { return projectName } return repoSplit[1].trim() }
但当是git代码库,同时仓库名有三层时,只取了仓库名中间的值去查询关联的流水线,这样会查出很多无效的流水线,导致流水线匹配时间变长,希望根据仓库类型计算projectNam的值
修复数据库的值时,应该考虑触发时兼容性问题,不影响流水线触发
The text was updated successfully, but these errors were encountered:
mingshewhe
hejieehe
No branches or pull requests
T_PIPELINE_WEBHOOK 记录代码仓库与流水线的绑定关系,表结构如下:
PROJECT_NAME 通过仓库名获取,这么写是因为工蜂svn触发时,仓库名为三层时,只需要取中间一层
但当是git代码库,同时仓库名有三层时,只取了仓库名中间的值去查询关联的流水线,这样会查出很多无效的流水线,导致流水线匹配时间变长,希望根据仓库类型计算projectNam的值
修复数据库的值时,应该考虑触发时兼容性问题,不影响流水线触发
The text was updated successfully, but these errors were encountered: