We want to establish an end-of-line check on all pushes to our Bitbucket server, to prevent Windows line-endings from being pushed to the repo.
I've found the stash-eol-check hook plugin, which provide this functionality on the repository level. However, it is a bit cumbersome to repeat the same configuration for each and every repository manually.
Is there a better way, to achieve this on project level or server level?
By chance, project level administration has just been introduced in Bitbucket Server 5.2:
"[...] Until 5.2, things like hooks, branch permissions and model, and pull request merge checks had to be configured each time a new repository was created. For teams that create hundreds (or even thousands) of repositories this can lead to wasted time or compromising on security requirements by granting admin permissions to people that might not necessarily need it. With the introduction of project level administration, these settings can now be applied to all repositories in a project at once, making implementing and enforcing your team's preferred workflow much easier. [...]"
So besides requiring an update to Bitbucket Server 5.2, this should allow configuration of your hook at the project level in a straight forward fashion.
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs