Details
Description
Initial discussion, see http://sonar.15.n6.nabble.com/sonar-dev-Create-project-in-advance-of-any-analysis-in-Sonar-td5003423.html
We are currently setting Sonar as part of a larger developer infrastructure. We have a project configuration phase where we create a SVN repo, setup a Jenkins view, create Jenkins jobs, assign LDAP roles to the subversion repo, the jenkins jobs, ... Unfortunately this security configuration cannot be done for Sonar at this point in time as Sonar has no project yet. The issue is that we do not know when the first Sonar analysis will run as this depends on the SVN project becoming populated by the project team and the a first successful Jenkins run. That means the project members need to write an email to the admin guys to associate their LDAP roles with the Sonar project after the first successful build. This is a situation we need to avoid here, which means we want to create an empty project and associate LDAP roles with the project at the time we setup all the other tools.
Attachments
Issue Links
- is related to
-
SONAR-4535 Make it possible to define default key patterns on permission templates
-
- Closed
-