Control freak -Jira Policy isn't working on some repos/forks but is effective on others.

[Murugan Mittapalli]

Hi Team,

We have configured the Control Freak settings at the project level so that all the repositories/forks follow the same security settings. However, some repositories/forks are compliant with the Jira Policy, while others are not. Please find the errors that users shared with us.

# Using GIT Bash I executed a push from my branch to the remote repository. I get the same Control Freak message that I did using VScode.

feature/CMM-41067-Darin-testing-retrofit
/c/GIT Repos MF/icg-mf-pnms-chile-fork
> git push
Enumerating objects: 61, done.
Counting objects: 100% (61/61), done.
Delta compression using up to 16 threads
Compressing objects: 100% (21/21), done.
Writing objects: 100% (21/21), 2.25 KiB | 2.25 MiB/s, done.
Total 21 (delta 20), reused 0 (delta 0), pack-reused 0 (from 0)
remote:
remote: Control Freak - Commit a2b535f5bf061fd5 rejected.
remote: -----
remote: Commit messages must satisfy the configured regex.
remote: Regex: ((?:\\\[CMM-[\\d]{5}\\].)|(?:\\\[H24-[\\d]{6}
].))
remote:
remote: Commit messages must follow the format of '[CMM-12345] desc' or '[H24-123456] desc'.
remote:
remote: Failing commit message: [Pull request #96: Feature/CMM-37925 mf reg baseline creation including code merges P02

‌

[Julius Davies [bit-booster.com]]

Sorry for our delay in responding. The new “Sortable Repos” feature in Control Freak v2024.05.28 ended up being so much work for the last month that we kinda accidentally denial-of-service attacked ourselves finishing it up!

Can you share more information? A screenshot of the Control Freak config pages would be helpful.

The commit message supplied there does not match the regex. I think a regex like this would make more sense:

((\[CMM-[\d]{5}\].)|(\[H24-[\d]{6}\].)).*

But their commit message would have to start with the characters “[CMM-37925]” instead of “Pull request #96”!

Alternatively you might find our “Jira Project Whitelist” control more intuitive. You could just pop “CMM, H24” into that whitelist (as a comma separated values) and also specify that Jira tickets must not have status “CLOSED” or “DONE”.

[Julius Davies [bit-booster.com]]

We are confident this issue was fixed in Control-Freak version v2024.10.05.

I’ve emailed Murugan Mittapalli directly. Based on his response I will either close this ticket are move it back to “open”.

‌