Control Freak - Commit Checks and Jira Hooks for Bitbucket

I have been using CF in a fairly large software development/CI environment for some time and it is working very well for me and my developers. The plugin is very flexible and for me, it was fairly intuitive to learn and configure. I appreciate the multi-level configuration capability which allows us to define an overall company/department policy, and then separate policies for specific projects or even individual repos. The vendor has responded to my requests for fixes and features quickly and efficiently, both by suggesting work-arounds to take care of the day to day right away and by discussing and implementing fixes.

While the idea an concept of the plugin is great, the support is not. There are many open issues / bugs, some open already since 2019 without a fix. Look at the issue tracker.

• 

  Bit-Booster Software

  Hi Sebastian, thanks for this review.

  Control-Freak v2020.09.22 was just published and includes a very exciting rebase/cherry-pick optimisation for Jira validation, support for multiple Jira application-links, support for renamed/moved Jira tickets, and the ability to specify "always-alllowed" new branch names for when the branching-model is getting in the way.

  Due to some staffing issues we faced from May - July we did not have much capacity to work on issues and enhancements, but we've fixed our staffing issues and we are now full steam ahead. Stay tuned for more Control Freak releases in the future!

This is a must-have app for any Bitbucket administrator. It does exactly what the name implies: enables "freakly controlling" various aspects, specially related to Jira integrations (make it very easy and straightfoward). Another feature that I couldn't find in other apps: it allows global control and per-repository control, which is awesome since one can enforce corporate patterns through global settings, and delegate other patterns to the repository owners. Like other users already said: 4 well deserved stars, and definitelly should be part of the default Bitbucket installation. Just a suggestion: it would be great to have the ability to customize messages when a push is rejected. Most of the builtin messages are pretty straightforward, but some of them can get a little confusing. Each setting could have a field to customize the message that is sent back when that rule fails. For example, we use a very complex regex to validate our branch naming pattern, and the rejection message just prints the regex and say it was not satisfied. If there was an option to customize the message, we could include some "easy to read" instructions instead of the developers needing to understand the pattern only by reading the regex on screen. Also, some custom header or footer (or both) would be helpful as well. I've seen these options in other plugins, and they are really cool features.

Hi Team , I have been using control freak plugin since a year now but i can see some issue here while validating the JIRA keys . In my configuration i'm using commit message regex and enabled Jira policy would be "anywhere in the commit message", so while validating it is considering and validating the JIRA as per RegEx and also it is considering and validating the reference Jira's in the whole commit message even though its not satisfy in the regex , the same is not happening if i select option "First line of the commit message" . Is this expected behavior or is a bug in the tool ? BR Ashok

• 

  Bit-Booster Software

  Control Freak's logic for finding JIRA keys is hard-coded, and CANNOT be controlled via the "Commit Messages Must Match Regex" control (which is a separate and independent control).

  Control Freak currently uses this Java regex for finding JIRA keys (hard-coded):

  • Pattern.compile("[A-Z][A-Z0-9]*-\\d+")

Hello! I defined "develop" as development branch, "master" as production branch in Repository Settings -> Branching model window of Bitbacket settings. Bun Control Freak uses terms "release branches" and "hotfix branches" for its customization. Where I can define release branch and hotfix for Control Freak?

• 

  Bit-Booster Software

  Hi!

  "release branches" and "hotfix branches" (and "bugfix" and "feature" as well) come from the "Branch prefixes" section of the Branching Model. To find this click on your repository (or project), and then click on --> settings --> Branching model.

  Note: If you disable the "Release" and "Hotfix" branch prefixes on that page, Control Freak defaults to using "release/*" and "hotfix/*" (similarly: "bugfix/*" and "feature/*"). Otherwise it uses whatever you've defined under your repository's Branching Model.

  2nd Note: the "New Branches Must Match Repository's Branching Model" control is more strict and does not fall back to any defaults if a given branching prefix is disabled. It simply disallows new branches that don't match the current active prefixes.