Has anyone tried this option enable retry using jobdsl ? enable retry itself missing under multijob - steps - phase ... in the plugin - https://jenkinsci.github.io/job-dsl-plugin/
Then on the job itself, under Build > MultiJob Phase > Advanced...: 1. Check "Enable retry" 2. Select strategy from the dropdown On Thursday, December 22, 2016 at 6:52:56 AM UTC+5:30 [email protected] wrote: > Thank you, I got it working for failures as well. > > On Wednesday, December 21, 2016 at 12:32:28 AM UTC-8, Vitaly Karasik wrote: >> >> You're right. >> The only catch is that there is no description/examples how to write >> rules. >> For instance, how to restart not only failed, but unstable jobs as well. >> At the end I just modify "unstable" status to "failure" in order to use >> rule for retry. >> >> On Thursday, October 15, 2015 at 4:44:09 PM UTC+3, 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/43f75967-ea53-49fa-813d-7569e4e42ea7n%40googlegroups.com.
