By default, the extension CI will not run when TiDB code updated to make sure the community contributor (and not pingcaper) not care too much about the enterprise version. But for some folders such as extension, if the code in them changed, we'd better to force trigger enterprise CI because enterprise code relies on it.
- When code changes in the below folders, trigger the extension UT in TiDB verify CI:
- When updating
pkg/extension/enterprise submodule version, check that the commit hash is the HEAD in the specified
enterprise repo branch.
By default, the extension CI will not run when TiDB code updated to make sure the community contributor (and not pingcaper) not care too much about the enterprise version. But for some folders such as
extension, if the code in them changed, we'd better to force trigger enterprise CI because enterprise code relies on it.pkg/extension/enterprisesubmodule version, check that the commit hash is the HEAD in the specifiedenterprise repo branch.