We're updating the issue view to help you get more done. 

Add the ability to disable mergeability filter

Description

We are having significant
performance problems with this plugin causing our event queue to fill up, and thus
causing events to start being dropped. This is NOT because all the event
threads are busy processing Jenkins notifications – I noticed that you improved
this in 4.4.3. Rather the problem is because of the “IsMergeableEligibilityFilter”
which appears to be running on all PullRequestRescope events? When looking at
the Diagnostics information, everytime events are being dropped we have a
thread dump of the event threads and all 32 of them are busy processing whether
some pull request is mergeable:
                              com.nerdwin15.stash.webhook.service.eligibility.IsMergeableEligibilityFilter.shouldDeliverNotification(IsMergeableEligibilityFilter.java:51)
                              com.nerdwin15.stash.webhook.service.eligibility.ConcreteEligibilityFilterChain.shouldDeliverNotification(ConcreteEligibilityFilterChain.java:26)
                              com.nerdwin15.stash.webhook.JenkinsEventListener.handlePullRequestEvent(JenkinsEventListener.java:91)
                              com.nerdwin15.stash.webhook.JenkinsEventListener.onPullRequestRescopedEvent(JenkinsEventListener.java:72)

We have custom plugins that run
very resource intensive merge-checks, and they are all constantly being
triggered by this plugin. Usually they only run when a user loads a PR in the
UI (or clicks the merge button).

How can we disable this feature?
Jenkins should receive the notification
regardless of whether the PR is mergeable.

Status

Assignee

Andrey Levchenko

Reporter

Mohammed Davoodi

Labels

None

Github URL

None

Sprint

None

Priority

Medium