title: How to use Jenkins pre-build branch merging only for branches I want to merge?
body: <p>I am reading <a href="https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-AdvancedFeatures">https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-AdvancedFeatures</a> which allows pre-builds of feature branches before pushing commits to the master branch, effectively implementing a pre-commit build/test queue.</p>
  
  <p>It says under <code>Using Git, Jenkins and pre-build branch merging</code>:</p>
  
  <blockquote>
    <p>Set up your Jenkins project, and leave the 'branch' field in the Git
    SCM blank. This will cause Jenkins to consider any change on any
    branch for building.</p>
    
    <p>Next, pick a particular branch name as the integration target in the
    'Advanced' section - (e.g. 'master', or 'stable'), and select 'Merge
    before build'.</p>
    
    <p>Select 'Push GIT tags back to origin repository' from the post-build
    actions (this is required to update your centralised git repo with the
    results of the build).</p>
    
    <p>Now, developers should never commit directly to your integration
    branch (the 'master' or 'stable'). Instead, they should either use
    feature branches, or create new remote branches on commit (e.g : "git
    push origin HEAD:refs/heads/myNewFeature"). You could also set up your
    GIT repository to only accept commits onto the integration branch from
    Jenkins.</p>
    
    <p>You're done. Commits should now be automatically merged with the
    integration branch (they will fail if they do not merge cleanly), and
    built. If the build succeeds, the result of the merge will be pushed
    back to the remote git repository.</p>
  </blockquote>
  
  <p>Now I often have feature branches that I would like to continue developing on, and only merge them into <code>master</code> later.</p>
  
  <p>As far as I understand, this setup will merge and push <em>any</em> feature branch into <code>master</code> as soon as it builds.</p>
  
  <p>(How) Can Jenkins support my use case, <strong>building all feature branches, but merging only those into <code>master</code> that I indend to be merged?</strong></p>