-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins ver. 2.107.2
Multijob 1.31
Here is how it configured:
Here is how the concerning rule looks like
> ls -la /var/lib/jenkins/rules/ total 32 drwxrwxr-x. 2 jenkins jenkins 4096 Dec 24 12:21 . drwxr-xr-x. 40 jenkins jenkins 12288 Mar 13 09:53 .. -rw-rw-r--. 1 jenkins jenkins 3 Jul 12 2017 retry_any_failure.txt -rw-rw-r--. 1 jenkins jenkins 18 Jul 12 2017 retry_failure.txt -rw-rw-r--. 1 jenkins jenkins 29 Dec 24 12:21 retry_unstable_failure.txt -rw-rw-r--. 1 jenkins jenkins 19 Jul 12 2017 retry_unstable.txt > cat /var/lib/jenkins/rules/retry_any_failure.txt .*
The concerning behavior is the following:
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.
How come everything (.*) from retry_any_failure.txt doesn't match the rules (©) ???
The important caveat here is that this behavior is intermittent; in most cases 
it works as expected, but this fact confuses even more than it wouldn't work at all...
Expected behavior
23:53:35 Finished Build : #456: [PR-654] of Job : another_job with status : FAILURE 23:53:35 Scanning failed job console output using parsing rule file /var/lib/jenkins/rules/retry_any_failure.txt. 23:53:35 Known failure detected, retrying this build. Try 1 of 1.
