In this page

FAQ

1 - What is the benefit of using the Better Commit Policy instead of hand-written hook scripts?

Reverting the question, there is no real advantage of using hand-written hook scripts instead of the app.
Please see this section.

2 - What Git/Subversion/Mercurial client can I use with the Better Commit Policy app?

You can use any client, including the commandline clients, IDE plugins, TortoiseSVN, etc.
Technically speaking, the only requirement is that the client must work according to the standards of the corresponding VCS (calling hooks, handling the standard input and output, etc.). It is true for any widely-used client.

3 - What is the difference between the Better Commit Policy and the Commit Acceptance Plugin?

Better Commit Policy is a modern, scalable, commercially supported re-implementation of the Commit Acceptance Plugin.
See this section for a comparison, and the migration guide for a step-by-step tutorial about converting your system from the legacy app to the modern one.

4 - I am using a version control system that is currently not supported. What should I do?

First off, tell about this to our support.
We are maintaining a public feature request list. Your request will be either added or upvoted (if already added).
In case you need a faster solution, we can explain the server-side API for you so that you can implement the hook script for yourself. Alternatively, you can use our implementation services and we will build the hook script for you.

5 - I want to verify a condition that is currently not supported. What should I do?

First off, tell about your condition to our support.
We are maintaining a public feature request list. Your request will be either added or upvoted (if already added).
In case your request is "too specific" to be included in the standard product or you need a faster solution, the Groovy condition allows implementing custom conditions in short Groovy scripts. Using this you can either develop the condition for yourself, or rely on our development services.

6 - I have unverified or non-compliant commits to push, how to disable the commit policy temporarily?

If you want to skip the verification just for one commit or one push, then make another commit, use the bypass pattern in its commit message, then push the changes.
If you want to skip the verification for a time longer than a couple of commits, then disable the policy itself (but don't forget to re-enable it later).

7 - What trial limitations are there while evaluating the app?

The following limitations are in place when using the app with a trial license:

  • After each commit verification, this snippet will be shown in the console: 
    ========================================================================
   *** VERIFIED BY BETTER COMMIT POLICY FOR JIRA - TRIAL VERSION ***
========================================================================
  • The security tokens in the hook scripts automatically expire every 2 months. Therefore, you have to generate new hook scripts if your trial takes longer than 2 months.
  • The global configuration option "Commits" menu visible for does not take effect. Therefore, you cannot hide the "Commits" menu from non-developers during your trial.

These limitations will be automatically removed as soon as you buy a supported license.

Questions?

Ask us any time.