Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
Jenkins 2.263.1; Bitbucket Server Integration 2.2.1; Bitbucket Server 7.5.0; Windows environment.
Description
Using the "Ignore on push notification" works, but only when I have just one Multibranch Pipeline Job for the repository. If I have a second one without the use of the option (shall build on push), the first one that shall ignore the push notification also builds on push to the repository.
Attachments
Activity
Knuth
added a comment - Hi Martin,
The "Bitbucket trigger scan after push" option was only active in the pipeline without the "ignore on push notification". Even if I remove the "Bitbucket trigger scan after push" on both and replace it with a daily scan, the "Ignore on push notification" pipeline will still get triggered on a push.
So this is not a workaround.
Knuth
added a comment - Hi Martin,
The "Bitbucket trigger scan after push" option was only active in the pipeline without the "ignore on push notification". Even if I remove the "Bitbucket trigger scan after push" on both and replace it with a daily scan, the "Ignore on push notification" pipeline will still get triggered on a push.
So this is not a workaround. 
Hi Knuth, thanks for the report.
One question about your setup- do both of your jobs have "Bitbucket trigger scan after push", and if not, is disabling it a viable workaround while we look into this issue?