166
Customers have installed this add-on in at least 166 active instances.
    by Tomas Bjerrefor Bitbucket Server 4.0.0 - 4.11.2 and more versions
    Versions available for Bitbucket Server 2.12.0 - 3.11.6
    Unsupported
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Unsupported
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Data Center
    This add-on is compatible with the clustering and high-availability capabilities of our products.
    Get it nowFree add-on

    Commit checker with focus on being informative and user friendly

    Commit checker with focus on being informative and user friendly

    Reject based on content of commit

    JQL

    Highly configurable rules organized in groups

    Commits can be rejected based on content of the commit. If it contains large files or if a custom regexp matches the content. Like an unresolved merge.

    Check that JQL query matches. Supporting variables for Stash user, email and custom regular expression (can be used to match JIRA).

    Example: issue = ${REGEXP} AND status = "In Progress" AND assignee in ("${STASH_USER}")

    Verifying existence of issue, or any other tag, in commits is easy. Or verifying that something is not mentioned is just as easy.

    More details

    Simple Stash Commit Checker rejects faulty commits. Highly configurable to give correct guidance to committers. Telling them whats wrong with the commits and how to correct it. It can check commits on push and/or pull requests.

    It can

    • Reject large files
    • Check changed content for regexp, like unresolved merge
    • Require committer, and/or author, email, and/or name, to match user (current or any) in Stash or regexp
    • Reject branch name not matching regexp
    • Reject based on JQL query
    • Highly configurable rules in groups. A group can be "issues" having rules in it for Jira or any other system
    • Used on all, or selected, branches
    • Run in "dry run"-mode. That accepts all commits, but may respond as if the commit was rejected. Also possible to supply a "dry run" message. This can be very useful when introducing the checker, a dry run period of a few days would give committers a chance to adjust to the new rules
    • General reject and/or accept messages
    • And more!

    Global settings with Settings Synchronizer

    User reviews

    (1)
    Sign in to write a review »
    by Fredrik Andersson [Sylog] on 2016-06-21
    We love the extensive settings this add-on provides us with. We just merged two AD used for Authentication and this added 7 times more users (~3000) and about 10 times more groups (~2000) in our directory. After this, the add-on is not possible to use. The performance is just to bad. Why, we don't know, yet.
    Was this review helpful?YesNo

    Pricing

    Support

    Simple Bitbucket Commit Checker isn't formally supported.

    Versions

    Version 2.9 Bitbucket Server 4.0.0 - 4.11.2 Released 2016-10-22

    Summary

    Variables in all configuration fields

    Details

    Enabling variables in all configuration fields. Allowing configuration that only allows a user to commit to branches like refs/heads/dev/${BITBUCKET_USER_SLUG}/.+.

    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 add-ons from the left-hand side of the page.
    4. Locate Simple Bitbucket Commit Checker via search. Results include add-on versions compatible with your Bitbucket instance.
    5. Click Install to download and install your add-on.
    6. You're all set! Click Close in the Installed and ready to go dialog.

    To find older Simple Bitbucket Commit Checker versions compatible with your instance, you can look through our version history page.

    Similar add-ons