I have concluded based on the answers above that the functionality is not in place and not in developments. The referred link is not relevant to my request.
You can help us to determine the community need for such a feature by voting on it over on the public Bitbucket issue tracker. Here is the link to the issue: https://bitbucket.org/site/master/issue/8322/add-clones-and-pushes-to-audit-logging-bb. This would give you nearly exactly what you are looking for. If we get enough votes, we'll consider it in the future.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for the reference. I may have been a bit unclear though, as that was not the same feature.
The feature I am looking for is to make sure that every time a user logs into the repository and downloads (or uploads) code this is logged and that the admin is able to review that "user access log". The use case is that Adam (head developer, Admin) is working with Charlie (developer paid by Adam) on code, with Ben acting as an advisor (and actually paying Adam and Charlie to do the work). As Ben is paying for the project he has a right to download code as a security measure in case Adam and Charlie stop developing. However, Ben is not allowed to download code as long as Adam and Charlie actively develop the code. This means Adam needs a tool to verify if Ben has downloaded code or not.
Hope this helps to better define the need.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Most likely auditing isn't on our immediate radar. I base that from our data backup policy which briefly covers this:
"One of the great features of distributed version control systems (DVCS) such as Git and Mercurial is that they're distributed. Backups are still very important, but consider that every person on your team that has forked your repository has a complete copy with a full history. Also, it's very easy to setup mirrors and automated backups to pull recent changesets."
More details here:
https://confluence.atlassian.com/pages/viewpage.action?pageId=288658413
This doesn't underscore the importance of maintaining audit trails however. With that, I was able to locate a feature request that seems relevant, although its not recent.
In any case, you might consider voting, commenting and watching #3738 for updates:
https://bitbucket.org/site/master/issue/3738/keep-an-audit-trail-of-changes-made-to-a
Hope this helps! :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.