Auditor for Bitbucket

Auditor for Bitbucket gives you the tools you need to enforce company policies, prevent data leaks, and breathe easy.

Prerequisites:

  • SSH support and SSH access keys are enabled on Bitbucket server
  • If you want to use the Migrate to Git LFS functionality you will need Git LFS support  enabled in Bitbucket and git-lfs tool is installed on the Bitbucket server.
  • User with ADMIN permission for all repositories which you want to impact. This user needs to be set in the Global Configuration.
  • Sufficient free disk space to perform modifications to repository. This can be up to 5x the size of your largest repository.
    • Repo + Backup + Working Copy + Working Copy during Pack (grows in size till completion then deletes old working copy) + SCM cache

Features:

Known Issues:

  • Pull request can be reopened while auditor is running (no corresponding cancellable event provided by bitbucket) causing push fail (https://community.atlassian.com/t5/Bitbucket-questions/Git-push-failure/qaq-p/283290)
  • Default hook.callback.buffer.capacity (5MB) is not enough to push mirror of large repositories. Workaround is to increase it via bitbucket.properties file or JVM parameters.
  • Large repositories post-recieve hook may fail with OutOfMemoryError in Bitbucket. Workaround is to increase the maximum heap size.
  • May fail with org.eclipse.jgit.errors.LargeObjectException$ExceedsLimit for some repositories. Workaround is to increase limit using “Max non-file object size” parameter in job configuration.