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 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+"
Does that help?
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