Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

Deprecated: This plugin has been removed from the Jenkins Update Centre

Please use the Naginator Plugin instead to retry a build after a failure.
Archived versions of this plugin remain available for download.

See also: Periodic Reincarnation Plugin

Plugin Information

No information for the plugin 'schedule-failed-builds' is available. It may have been removed from distribution.

Allows you to retry failed Hudson builds every n minutes.
The number of retries can be configured as well.

Change Log

Version 1.1 (2009-12-28)
Version 1.0 (2008-09-19)
  • Initial release


  1. Unknown User (jminne)

    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.jenkins-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.

  2. Unknown User (nele_lav@yahoo.ca)

    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?

  3. Unknown User (kmart)

    It does work but you need to click the check box under Build Triggers first:

     Schedule failed Builds regularly (see Retry interval @ScheduleFailedBuildsPublisher)

    and then:

    Schedule failed builds


    Retry interval (minutes)









    Max. retries




  4. Unknown User (jl.pinardon)

    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.

  5. Unknown User (dtka)

    It did not work after first trial, maybe I missed something in the configuration. Moved to Naginator :/

  6. Unknown User (chemmo)

    I don't really understand why its necessary to have two checkboxes (one in build triggers the other in post-build actions) and for them both to be ticked for this to work. Why not just have the one in post-build actions? This plugin is not very well documented, it needs the help ("?" icon's) to be added to the checkboxes with information.