title: How to set non-default quality gate for new sonar projects
body: <p>We use jenkins, sonarqube 5.5, maven and git. When developers create a new git branch and push it, jenkins analyses the branch too, so the developers can fix everything before merging. To avoid this development branch analysis mixing up with the master branch analysis, jenkins passes the branch name into the analysis. The causes sonarqube to create a new project for each branch. So far that's ok.</p>
  
  <p>But recently we switched from one default quality gate for all projects to different quality gates for projects under active development and projects which are just in maintenance.</p>
  
  <p>So how can we tell sonar when creating an new project for a new branch which quality gate to use? Until some versions ago, there was a sonar.qualitygate property which could be set. But now this is deprecated. So what's the new way to define the proper quality gate for a newly created project?</p>