-
Suggestion
-
Resolution: Fixed
-
13
-
Hi all,
I'm excited to share that in Bitbucket Server 7.1 we shipped Push log feature that allows admins to see the history of all push events in a repository.
You can find more information in the Bitbucket Server 7.1 release notes and Push log docs.
Please, don't hesitate to leave feedback on the feature in the comments. This will help us to priorities further development.
Anton Genkin
Product Manager Bitbucket Server
Original message
As and administrator, I would like to be able to have push events moved to a higher priority so I do not have to set my audit log capture to low in order to get these events.
Since Git allows users to specify what they wish in their .gitconfig file for user name, it is at the Stash authentication level for push events that we consider the audit point for determining who is responsible for a set of changes. If you push it, even if you don't author it, you are considered the owner of the changes. The audit log feature for Stash does allow us to capture this information so we can tie the push of particular commits to the Stash authenticated user. The push events, however are classified as low priority so unless we are missing something, we need to set the audit log level to low. This would then capture many events that we are not interested in. From our standpoint and the need for more stringent audit trails, we feel that push events should be classified at more than a 'low' priority.
- is incorporated by
-
BSERV-5141 Make audit event logging more flexible
- Closed
-
BSERV-10796 Make audit event logging more flexible
- Closed
- is related to
-
BSERV-2642 Push Traceability
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...