Multiple triggers of the commits on initialization of the jobs about bitbucket-push-and-pull-request-plugin

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[cdelmonte-zg]

Hello @josemonsalve2

here are the results of the investigation:

Premise: the Bitbucket Push and Pull Request Plugin, starting from this point simply called BBPPR Plugin, uses the Git Plugin to handle with the git repositories managed by BitBucket.

1. The user initiliazes a new job starting manually a build.
2. The Git Plugin clones the declared repository fetching the branches as defined in the Branch Specifier filter field.
3. Each branch is new, that means that the BBPPR Plugin sees everywhere changes
4. As a consequence, the BBPPR Plugin starts for each fetched branch a job.
5. It's also important to keep in mind that the filters on the branches specified by the BBPPR Plugin in its Allowed Branches field, are not applied in the initialization phase, because they are only active for jobs triggered through the BitBucket webhook (and not for the ones, which are built manually).

More in general and to summarize:

• the Git Plugin filter on the branches is a kind of general filter applied at job level.
• the BBPPR Plugin filter is a specific one, that acts at trigger level and it is there because the user can have in a job more triggers than one.