Hi Michael,
We have purchased and been using Sonar for Bitbucket, it is a great tool. Recently we are starting off a few high-confidential project that we don't want any developer to see the source code. In Sonar, we can assign members into a group and then have that project only visible to such group.
The problem with what we have now is that it seems the feature branch does not seems to inherit these permission, so turns out everyone can see the source. Any thoughts?
Thanks,
Terry
Hi Terry,
Thanks for your question. I think SonarQube already supports your use case with the concept of permission templates. As far as I know you can specify your permissions with a new template and provide a regex for a project key that applies to all new branches (i.e., projects), something like "com\.yourcompany\.confidentialprojectname:\w+"
image2016-9-22 11:1:27.png
Does that help?
Best regards,
Michael
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.