JIRA + Crucible - Commit Acceptance plugin and update reviews

[Seth Jackson]

I have JIRA v5.2 linked with Crucible v2.9 running the Commit Acceptance v1.6 plugin. The CA plugin is configured to require a valid ticket to commit.

However, when trying to use smart commits to update a Crucible review, the Crucible review treated as a JIRA ticket, which is validated against JIRA, and the CA check fails.

E.g.

Commit comment - ISSUE-123 Added code to fix bug. +review CRUCIBLEPROJECT

* This works great and creates review CRUCIBLEPROJECT-1

Subsequence commit comment - ISSUE-123 Added mode code to fix last code. +review CRUCIBLEPROJECT-1

CA precommit hook fails with:

Commit rejected: Issue [CRUCIBLEPROJECT-1] does not exist or you don't have permission to access it.

Edit (11/072014): I've posted this as a bug: https://jira.atlassian.com/browse/JRA-35698

[Midori]

Commit Policy Plugin is a replacement for the Commit Acceptance Plugin, and it supports defining a regular expression to parse JIRA issue keys from commit message. You can use that expression to ignore the snippets that refer to a Crucible review, not to a JIRA issue.

This is exactly the use case why we allow configuring this pattern.

Example:

(?:\s|^)(?!REQ)[A-Z]+\-\d+(?:\s|$)                           ## ignores REQ-123 strings
(?:\s|^)(?!REQ|UITEST)[A-Z]+\-\d+(?:\s|$)             ## ignores REQ-123 and UITEST-456 strings

See: http://www.midori-global.com/products/jira-commit-policy-plugin/documentation#issue-key-pattern

[AhmadDanial]

Hey there, Seth.

Are you still facing problems with this issue? If yes, I would suggest you to reach out to the support engineers by raising a ticket in https://support.atlassian.com so they can help you to tackle this problem. Hope this helps.