[JIRA] (JENKINS-56539) Multijob Retry Rules: failure doesn't match the rules
Title: Message Title Sasha Miroshnychenko commented on JENKINS-56539 Re: Multijob Retry Rules: failure doesn't match the rules 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) - job: name: My_Pipeline node: pipeline project-type: multijob parameters: - string: name: my_param wrappers: - timestamps builders: - multijob: name: Example subjob condition: SUCCESSFUL projects: - name: paralleled_executor current-parameters: true kill-phase-on: NEVER retry: max-retry: 1 strategy-path: "/var/lib/jenkins/rules/retry_any_failure.txt" As you can see strategy-path: "/var/lib/jenkins/rules/retry_any_failure.txt" 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: UnstableOrFailure: /var/lib/jenkins/rules/retry_unstable_failure.txt which is: > cat /var/lib/jenkins/rules/retry_unstable_failure.txt Finished: (FAILURE|UNSTABLE) 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. Add Comment
[JIRA] (JENKINS-56539) Multijob Retry Rules: failure doesn't match the rules
Title: Message Title Sasha Miroshnychenko updated an issue Jenkins / JENKINS-56539 Multijob Retry Rules: failure doesn't match the rules Change By: Sasha Miroshnychenko Attachment: retry_any.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56539) Multijob Retry Rules: failure doesn't match the rules
Title: Message Title Sasha Miroshnychenko updated an issue Jenkins / JENKINS-56539 Multijob Retry Rules: failure doesn't match the rules Change By: Sasha Miroshnychenko Attachment: image-2019-03-13-12-55-35-279.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56539) Multijob Retry Rules: failure doesn't match the rules
Title: Message Title Sasha Miroshnychenko created an issue Jenkins / JENKINS-56539 Multijob Retry Rules: failure doesn't match the rules Issue Type: Bug Assignee: Unassigned Attachments: image-2019-03-13-11-50-08-020.png Components: multijob-plugin Created: 2019-03-13 10:30 Environment: Jenkins ver. 2.107.2 Multijob 1.31 Priority: Minor Reporter: Sasha Miroshnychenko 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 jenkins18 Jul 12 2017 retry_failure.txt -rw-rw-r--. 1 jenkins jenkins29 Dec 24 12:21 retry_unstable_failure.txt -rw-rw-r--. 1 jenkins jenkins19 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
