Currently it works in the way that we only push and delete when the build result is SUCCESS. Jenkins has a state in between failure and success that is UNSTABLE, if a test for some reason fails in an indeterministic manner, some might consider 1 failing unit test OK for the gatekeeper. If the result in the case is UNSTABLE the merge commit on the feature is not pushed to the integration branch.
This feature would allow the user to configure an unstable build result good enough for gate-keeping.