Great answer Aleksander. This feature should definetly be better documented.
In my case I found out that if if your task finishes with "UNSTABLE" instead of "FAILURE", phase retry configuration has no effect. El martes, 10 de mayo de 2016, 12:14:33 (UTC+2), Aleksandar Kasabov escribió: > > 1) Make a parsing rule file, e.g. /var/lib/jenkins/rules/failures.txt with > content 'Finished: FAILURE' > 2) Register that in Jenkins general config, section "Multijob Retry Rules > -> Parsing Rules" > 3) Use that rule in the job that you want to be retried, the field is > "Select strategy" which right below the "Enably retries" in the multiphase > project settings > > In general, move to the the pipeline plugin, Multijob plugin is quite old, > not to mention the quality of the java source code it's writen in > Good luck > > On Thursday, January 14, 2016 at 11:25:17 AM UTC+1, Zheng LiSheng wrote: >> >> My problem is that nothing happens after selecting "Enable retry". >> >> On Thursday, October 15, 2015 at 9:44:09 PM UTC+8, Kris Massey wrote: >>> >>> Hey All, >>> >>> I'm new to the Jenkins MultiJOb plugin and I'm having some troubles >>> using the retry functionality. >>> >>> I have a job configured >>> >>> MultiJob >>> - Phase 1 >>> - Job 1 >>> - Job 2 >>> - Phase 2 >>> - Job 3 >>> >>> >>> Job 2 can have random failures (due to external client system), I've >>> noticed that the MultiJob -> Phase -> Job configuration offers a 'Enable >>> retry' option, so I was hoping this would then attempt a retry and kick off >>> phase 2 if the job passed the second time. >>> >>> My issue is the retry never seems to happen, below is some output on the >>> console of the MultiJob >>> >>> [EnvInject] - Loading node environment variables. >>> Building in workspace /var/lib/jenkins/jobs/build-process/workspace >>> >> Job status: [Job2] the 'build only if scm changes' feature is >>> disabled. >>> Starting build job p2 <http://jenkins.inf.dev.underwriteme.co.uk/job/p2/>. >>> >> Job status: [Job1] the 'build only if scm changes' feature is >>> disabled. >>> Starting build job p1 <http://jenkins.inf.dev.underwriteme.co.uk/job/p1/>. >>> Finished Build : #21 >>> <http://jenkins.inf.dev.underwriteme.co.uk/job/p2/21//> of Job : Job2 with >>> status : FAILURE >>> <http://jenkins.inf.dev.underwriteme.co.uk/job/p2/21//console>*Scanning >>> failed job console output using parsing rule file . >>> Parser rules file not found.* >>> Failed the build, the failure doesn't match the rules. >>> Finished Build : #23 >>> <http://jenkins.inf.dev.underwriteme.co.uk/job/p1/23//> of Job : J >>> <http://jenkins.inf.dev.underwriteme.co.uk/job/p1/>ob1 with status : >>> SUCCESS <http://jenkins.inf.dev.underwriteme.co.uk/job/p1/23//console> >>> Build step 'MultiJob Phase' marked build as failure >>> Notifying upstream projects of job completion >>> Warning: you have no plugins providing access control for builds, so >>> falling back to legacy behavior of permitting any downstream builds to be >>> triggered >>> Finished: FAILURE >>> >>> >>> I've highlighted the lines I believe may be causing the issue, however I've >>> got no idea how to solve it (hopefully its missing config as apposed to a >>> bug in the MultiJob plugin) >>> >>> >>> Any help greatly appreciated! >>> >>> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/46cd23a9-fa89-43fa-b226-586ac1ccb27b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
