Alexander Link just added some improved help for the branch selection field. That may help you see how you need to specify the branch name in order to achieve the result you want.
Refer to https://github.com/jenkinsci/git-plugin/commit/48583bf82e8f563cd5368e1567b11e4190959eae for the details. I believe the key change needed for that improvement is included in git-client-plugin 1.6.4, and is not available in git-client-plugin versions prior to 1.6.4.
The behavior you observe (aaa/master is not treated any differently than origin/master) is an expected behavior that we didn't want to change, lest it break compatibility with existing user jobs. Alexander added the ability to provide a more precise specification of the branch name, while still retaining the older behavior for simpler branch names.
Can you review his comments and try them with git-client-plugin 1.6.4 to see if they resolve your issue?
Alexander Link just added some improved help for the branch selection field. That may help you see how you need to specify the branch name in order to achieve the result you want.
Refer to https://github.com/jenkinsci/git-plugin/commit/48583bf82e8f563cd5368e1567b11e4190959eae for the details. I believe the key change needed for that improvement is included in git-client-plugin 1.6.4, and is not available in git-client-plugin versions prior to 1.6.4.
The behavior you observe (aaa/master is not treated any differently than origin/master) is an expected behavior that we didn't want to change, lest it break compatibility with existing user jobs. Alexander added the ability to provide a more precise specification of the branch name, while still retaining the older behavior for simpler branch names.
Can you review his comments and try them with git-client-plugin 1.6.4 to see if they resolve your issue?