While I'm fairly confident that this issue caused by an implicit misconfiguration on my end, there is still some kind of magic plugin behavior as well...
I decided to double check the job configuration UI and noticed this
Normally, this would never happen since all my ~1k jobs are configured with JJB, like this (multijob)
name: Example subjob
- name: paralleled_executor
As you can see
that is being obviously mentioned in multijob logs
00:57:40 Finished Build : #321: [PR-123] of Job : paralleled_executor with status : FAILURE
00:57:40 Scanning failed job console output using parsing rule file /var/lib/jenkins/rules/retry_any_failure.txt.
00:57:40 Failed the build, the failure doesn't match the rules.
... in reality, doesn't match to the rule from the global jenkins configuration:
> cat /var/lib/jenkins/rules/retry_unstable_failure.txt
I ended up adding 4th rule with that desired rule-file
... and after re-uploading job it shows proper rule (Any) from job configuration UI.