749
Customers have installed this app in at least 749 active instances.
749
Customers have installed this app in at least 749 active instances.
    by Bit-Booster Softwarefor Bitbucket Server 5.8.0 - 7.4.0, Bitbucket Data Center 5.8.0 - 7.4.0 and more versions
    Versions available for Bitbucket Server 4.13.0 - 5.7.4
    Supported
    Bit-Booster Software supports this app.

    Get support

    Supported
    Bit-Booster Software supports this app.

    Get support

    Get it nowFree app

    Incredibly powerful and flexible Git push & merge hook. Better than YACC, easier to use than ScriptRunner. Great Jira integration

    Incredibly powerful and flexible Git push & merge hook. Better than YACC, easier to use than ScriptRunner. Great Jira integration

    Incredibly powerful and flexible Git push & merge hook. Better than YACC, easier to use than ScriptRunner. Great Jira integration

    Ensure Your Team Follows Best Practices With Git

    Helpful Reject Messages Keep Developers Productive

    Not Just Yet Another Jira Hook for Bitbucket

    - Enforce a rebase, squash, or git flow policy

    - Prevent repos with bad defaults (e.g. "master" can be deleted!)

    - Run a Gerrit work flow (e.g. "Needs Work" PRs can't merge)

    - Prevent costly --force or --mirror mistakes

    - Control Freak's rejection messages include specific steps to fix the problem

    - Developers less likely to pester and distract their team's top git expert for help

    - Able to fix their own git commit mistakes immediately

    - Define protected branches using Bitbucket's branching model

    - All pushes and merges are checked, including from forks

    - Jira checker can look at status, assignee, or arbitrary JQL

    - Flexible config (e.g. ignore merges)

    Ensure Your Team Follows Best Practices With Git

    Helpful Reject Messages Keep Developers Productive

    Not Just Yet Another Jira Hook for Bitbucket

    - Enforce a rebase, squash, or git flow policy

    - Prevent repos with bad defaults (e.g. "master" can be deleted!)

    - Run a Gerrit work flow (e.g. "Needs Work" PRs can't merge)

    - Prevent costly --force or --mirror mistakes

    - Control Freak's rejection messages include specific steps to fix the problem

    - Developers less likely to pester and distract their team's top git expert for help

    - Able to fix their own git commit mistakes immediately

    - Define protected branches using Bitbucket's branching model

    - All pushes and merges are checked, including from forks

    - Jira checker can look at status, assignee, or arbitrary JQL

    - Flexible config (e.g. ignore merges)

    More details

    Control Freak is a collection of push and merge hooks to reject commits based on pre-configured rules. Available rules include:

    • Enforce JIRA linking for git commit messages
    • Branch naming policy
    • Block large files
    • Block branch deletes / rewrites / force-pushes of important branches
    • Enforce a rebase / squash workflow
    • Enforce a pull-request workflow
    • Block self-approvals on pull-requests
    • Author / committer name and email checks
    • Block empty commits
    • Block foxtrot merges

    Configuration can be applied per-repo, per-project, or globally. Rules can be applied per repository type (regular vs. personal vs. fork). User and Group based exemption lists let service accounts, bots, and power users avoid the checks when necessary.

    Our checking logic is optimized to run at most two "git rev-list" commands per push or merge, no matter how many rules you have enabled.

    ---

    ABOUT BIT-BOOSTER

    We also make:

    More details

    Control Freak is a collection of push and merge hooks to reject commits based on pre-configured rules. Available rules include:

    • Enforce JIRA linking for git commit messages
    • Branch naming policy
    • Block large files
    • Block branch deletes / rewrites / force-pushes of important branches
    • Enforce a rebase / squash workflow
    • Enforce a pull-request workflow
    • Block self-approvals on pull-requests
    • Author / committer name and email checks
    • Block empty commits
    • Block foxtrot merges

    Configuration can be applied per-repo, per-project, or globally. Rules can be applied per repository type (regular vs. personal vs. fork). User and Group based exemption lists let service accounts, bots, and power users avoid the checks when necessary.

    Our checking logic is optimized to run at most two "git rev-list" commands per push or merge, no matter how many rules you have enabled.

    ---

    ABOUT BIT-BOOSTER

    We also make:

    Reviews for cloud

    (7)Sign in to write a review

    There are no reviews yet. Be the first to review this app.

    Reviews for server

    (7)
    Sign in to write a review
    by Antonio Matos - Raízen on 2020-01-28
    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.
    Was this review helpful?YesNo
    by Ashok G on 2019-11-11
    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
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    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+")
    by Konstantin Z. on 2019-03-12
    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?
    Was this review helpful?YesNo
    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.

    by Charlie Misonne on 2018-12-14
    This app for Bitbucket Server is great! No need to write a custom script to do check commit messages for Jira issue keys. The configuration can be applied per repository type, at the project level and at the repository level. This gives a lot of flexibility. Exactly what we needed!
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Jean-Pol Landrain on 2018-09-25
    This plugin set rules for a usage of Git/Bitbucket that respect and enforces best practices. Everything is configurable in order to adapt to your own usage and there are multiple levels of configuration that you can combine: globally, per project and/or per repository. One of the most clever plugin for Bitbucket. The only possible improvement I can see now is related to the documentation: it should explain a bit more the concepts (e.g.: why a git push -f can cause a disaster when push.default=matching), and it would maybe be convenient to integrate the documentation directly into the plugin. But did I mention this plugin is free ? 5 stars well deserved: should be part of every Bitbucket installation.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo

    Reviews for Data Center

    (7)Sign in to write a review

    There are no reviews yet. Be the first to review this app.

    Cloud Pricing

    Server Pricing

    Data Center Pricing

    Bit-Booster Software provides support for this app.

    Bit-Booster Software provides support for this app.

    Vendor support resources

    Documentation

    Find out how this app works.

    Community

    Community discussions connect you to the vendor and other customers who use this app.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this app.

    Vendor support resources

    Documentation

    Find out how this app works.

    Community

    Community discussions connect you to the vendor and other customers who use this app.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this app.

    Versions

    Version 2020.05.05 Bitbucket Server 5.8.0 - 7.4.0 Released 2020-05-06

    Summary

    One new enhancement (ability to ignore access-keys / service accounts)

    Details

    Full changelog below the fold.

    ---

    If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket Server. Revenue from PR-Booster helps fund Control Freak's maintenance.

    ---

    One new enhancement:

    • Control-Freak rules can now be ignored when pushes come from access keys (a.k.a.service accounts).

    In future versions of Control Freak we may consider tying the exemption to specific access keys, but for now it's an all-or-nothing style control (e.g., allow all service accounts to skip the rules, or force all service accounts to follow the rules). This exemption can be set at the global, project, or repository level. It defaults to requiring service accounts to follow all rules (the current behavior).

    Versions

    Version 2020.05.05 Bitbucket Data Center 5.8.0 - 7.4.0 Released 2020-05-06

    Summary

    One new enhancement (ability to ignore access-keys / service accounts)

    Details

    Full changelog below the fold.

    ---

    If you find Control Freak useful please consider purchasing a license for our paid app: PR-Booster for Bitbucket Server. Revenue from PR-Booster helps fund Control Freak's maintenance.

    ---

    One new enhancement:

    • Control-Freak rules can now be ignored when pushes come from access keys (a.k.a.service accounts).

    In future versions of Control Freak we may consider tying the exemption to specific access keys, but for now it's an all-or-nothing style control (e.g., allow all service accounts to skip the rules, or force all service accounts to follow the rules). This exemption can be set at the global, project, or repository level. It defaults to requiring service accounts to follow all rules (the current behavior).

    Installation

    1. Log into your Bitbucket instance as an admin.
    2. Click the admin dropdown and choose Add-ons. The Manage add-ons screen loads.
    3. Click Find new apps or Find new add-ons from the left-hand side of the page.
    4. Locate Control Freak for Bitbucket Server via search. Results include app versions compatible with your Bitbucket instance.
    5. Click Install to download and install your app.
    6. You're all set! Click Close in the Installed and ready to go dialog.

    To find older Control Freak for Bitbucket Server versions compatible with your instance, you can look through our version history page.

    1. Log into your Bitbucket instance as an admin.
    2. Click the admin dropdown and choose Add-ons. The Manage add-ons screen loads.
    3. Click Find new apps or Find new add-ons from the left-hand side of the page.
    4. Locate Control Freak for Bitbucket Server via search. Results include app versions compatible with your Bitbucket instance.
    5. Click Install to download and install your app.
    6. You're all set! Click Close in the Installed and ready to go dialog.

    To find older Control Freak for Bitbucket Server versions compatible with your instance, you can look through our version history page.

    Similar apps