Allows you to retry failed Hudson builds every n minutes.
The number of retries can be configured as well.
Feb 22, 2010
Just for reference I wanted to note that this(Retry Failed Builds) is similar to but not the same as the Naginator plugin. http://wiki.hudson-ci.org/display/HUDSON/Naginator+Plugin That one re-tries 5 minutes, then 10, moving up to an hour. It also has a regex checking option.
This one allows you to specify the delay between retries and maximum number of re-tries.
I guess these 2 plugins could eventually be combined but for now both are useful in their own way.
May 13, 2010
I tried this and did not work. I configured my project to retry twice when failed with an interval of 1 minute. It did not retry to build when my project build failed. How to use this plugin?
Sep 02, 2010
It does work but you need to click the check box under Build Triggers first:
Schedule failed Builds regularly (see Retry interval @ScheduleFailedBuildsPublisher)
Sep 29, 2010
Thanks for the job.
Works well but as Ken Martin says, the configuration needs attention.
Also something annoying to underline : it does not work correctly with the Join plugin.
Let's consider :
|-- Job B1
|-- /Join/ -- Job C
|-- Job B2
If a retry is configured for Job B1 and Job B1 fails, the Join triger does not fire. Job B1 is retried, OK, _but the Join does not fire when Job B1 succeeds._I don't know if it is a problem tied to the Retry plugin or to the Join plugin, but it is really annoying in the case of complex job flow.
I have logged and issue (7604 ) on the schedule failed build component, but I guess it could also be tied to join component...
Well, nevertheless, thanks for the job.
Feb 16, 2011
Thanks for the plugin
Powered by a free Atlassian Confluence Open Source Project License granted to Hudson.