Commit Acceptance Plugin Reject Commits due to Other String similar to Issue Key
プラットフォームについて: Data Center のみ。 - This article only applies to Atlassian apps on the Data Center プラットフォーム。
この KB は Data Center バージョンの製品用に作成されています。Data Center 固有ではない機能の Data Center KB は、製品のサーバー バージョンでも動作する可能性はありますが、テストは行われていません。 Server* 製品のサポートは 2024 年 2 月 15 日に終了しました。Server 製品を実行している場合は、 アトラシアン Server サポート終了 のお知らせにアクセスして、移行オプションを確認してください。
*Fisheye および Crucible は除く
症状
Often we might need to refer some string that looks like issue key such as ISO standard or other products key such as Crucible review. For example, ISO-8859 was recognized as issue key although it is a ISO standard that has a string like Issue Key. This caused the string to be recognized and rejected by the plugin due to the non-existence of the project in JIRA.
The following appears when you tried to commit the message with string similar to Issue Key:
Commit message: "TEST-123 The contents of documents have to convert from ISO-8859-1 to UTF-8 character encoding"
Commit rejected: Issue [ISO-8859] does not exist or you don't have permission to access it.原因
Part of the problem seems to rely on the Project Key Pattern in JIRA in recognize the issue key in commit message. There's a bug reported on this behaviour: https://ecosystem.atlassian.net/browse/CMMT-18
回避策
A different project key pattern such as ([A-Z]{4}+) can be use to avoid string such as ISO-XXX or UTF-8 being recognized as issue key during the commit acceptance process. However, such workaround only applies if you're using at least 4 letters projects and reference of 3 letters string such as ISO-XXX. If you have been using 4 letters project key and often refer to 4 letters strings similar to issue key, the workaround may not applies to you.
この内容はお役に立ちましたか?