If a developer creates a feature branch and a corresponding Pull-Request, we wind up with two jobs doing basically the same thing. Once for the branch itself, and one labeled with the Pull Request Number.

Scenario: Create a feature/whatever and open a PR to merge to master:

• When a feature/whatever branch is created a build is trigger.
• When a PR is open to merge feature/whatever to development, the PR project is created in Jenkins, triggering the "same build" as above.

It would be nice to have the option to disable this behavior.