Naginator Plugin

Skip to end of metadata
Go to start of metadata

Plugin Information

Plugin ID naginator Changes In Latest Release
Since Latest Release
Latest Release
Latest Release Date
Required Core
Dependencies
1.15 (archives)
Apr 09, 2015
1.554
matrix-project (version:1.2)
Source Code
Issue Tracking
Pull Requests
Maintainer(s)
GitHub
Open Issues
Pull Requests
Andrew Bayer (id: abayer)
Nicolas De Loof (id: ndeloof)
Tomer Galun (id: galunto)
Usage Installations 2014-May 1672
2014-Jun 1762
2014-Jul 1891
2014-Aug 1937
2014-Sep 2043
2014-Oct 2220
2014-Nov 2320
2014-Dec 2385
2015-Jan 2521
2015-Feb 2599
2015-Mar 2877
2015-Apr 2915

Description

This plugin allows you to automatically reschedule a build after a build failure.
This can be useful in several cases, including:

  • The build is dependent upon external resources, that were temporarily unavailable (DB down, network down, website down, etc).
  • Users want continuous emails sent out until the build is fixed, in order to prompt people into action.

Configuration

Simply install the plugin, and then check the Post-Build action "Retry build after failure" on your project's configuration page.

If the build fails, it will be rescheduled to run again after the time you specified. You can choose how many times to retry running the job. For each consecutive unsuccessful build, you can choose to extend the waiting period.

The following options are also available:

  • Rerun build for unstable builds as well as failures
  • Only rebuild the job if the build's log output contains a given regular expression
  • Rerun build only for the failed parts of a matrix job

The plugin also adds a rerun button for in the build section.

Version History

Version Unreleased. (No due date)

  • Fix plugin javadocs
  • Preserve cause history
  • Add environment variables with the value of retry count and number of retries left
  • Added the option to prevent manual retry on a job

Version 1.15 - Apr 9, 2014

  • Make JobProperty optional for jobs
  • Decrease require core for ancient jenkins users

Version 1.14 - Dec 19, 2014

Version 1.13 - Nov 12, 2014

  • Fix progressive delay time calculation (behavior slightly changed)
  • Fix rerun behavior for unstable builds in matrix
  • Better log the trigger cause
  • Fix badge icon for the case in which Jenkins is not in the root folder
  • Don't show rerun link if user doesn't have permissions

Version 1.12 - Aug 25, 2014

  • Added the option to rerun only the failed parts of a matrix
  • Retry will occur only when all parts of a matrix finish
  • Rebuild link verify authentication
  • Don't rerun job on manual cancel
  • Fix NPE when running Maven build

Version 1.11 - April 8, 2014

  • Naginator now retain original build causes on retry

Version 1.9 - Nov 8, 2013

  • Re-schedule limit doesn't consider previous builds that aren't related to Naginator
  • Added a badge icon to re-scheduled builds
  • Bug fixes

Version 1.8 - June 12, 2012

  • New extension point to configure schedule delay
  • Fixed delay implementation
  • Parameters for build are reused on schedule
  • Limit for number of build attempts after failure

Version 1.7 - May 31, 2012

Version 1.6.1 - May 3, 2012

  • Fix compatibility with build-timeout plugin (JENKINS-11594)
  • Use a RunListener

Version 1.6

  • Not released (release:prepare failed on ndeloof computer :-/)

Version 1.5 - Dec 7, 2009

  • Added support for not rebuilding if the build is unstable.
  • Added support for only rebuilding if a regular expression is found in the build log.

Version 1.4 - Jan 26, 2009

  • The plugin progressively introduces a delay until the next build. It starts with 5 minutes and goes up to one hour.

Version 1.3 - April 9, 2008

  • After way too long, the release is actually out there. 1.1 and 1.2 are missing due to my inability to use the maven release process correctly  .

Version 1.0 - Sept 17, 2007

  • Initial Release - release didn't actually make it to the repository...

Labels

plugin-trigger plugin-trigger Delete
nag nag Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Jan 23, 2009

    Christoph Kutzinski says:

    I'm not quite sure what reschedule means in this case? Is the next build started...

    I'm not quite sure what reschedule means in this case? Is the next build started immediately after the failed build (possibly delyed by the quiet period?)?

    It would be very helpful to have a cooldown period before rescheduling the build. IMO it is very probable that an external resource is still unavailable when you restart the build immediately. But if you wait for some time chances are higher that it is available again.

    Edit: I just found out that the schedule-failed-builds plugin does something like that.

  2. Jul 04, 2011

    Daniel Tkatch says:

    Would be cool to have an option to rebuild a failed/unstable parametrized build ...

    Would be cool to have an option to rebuild a failed/unstable parametrized build with the same parameters. This are getting lost at the moment. A bit like Rebuild Plugin, but automatically.

  3. Jul 16, 2012

    Ming Zhu says:

    Excellent plugin in. Thank you!

    Excellent plugin in. Thank you!

  4. Feb 14, 2013

    Dave Abrahams says:

    Strange, I don't see the "Reschedule build after failure" checkbox anywhere on m...

    Strange, I don't see the "Reschedule build after failure" checkbox anywhere on my project's configuration page.  What am I missing?

    (yes, the plugin is installed).

    1. Aug 26, 2013

      robertbw says:

      I have the same issue. It doesn't re-run my build so I'm trying to find out why ...

      I have the same issue. It doesn't re-run my build so I'm trying to find out why and I don't see that checkbox either. Is the description up to date?

      1. Dec 10, 2013

        dilipm79 says:

        It seems to be under Post Build section as "Retry build after failure"

        It seems to be under Post Build section as
        "Retry build after failure"

  5. Mar 26, 2013

    zioschild says:

    We're using the plugin since a long time and especially for network-jobs with un...

    We're using the plugin since a long time and especially for network-jobs with unstable connections this plugin works great. Thx.
    But...
    Am I right: aborting a build manually will cause a rebuild as well? Is it possible to suppress (manually) aborted jobs from rebuild?

    1. Sep 03, 2014

      galunto says:

      Solved now

      Solved now

  6. Mar 26, 2013

    tmcmurra says:

    Can anyone point me to info on configuring this plugin. I installed it but my jo...

    Can anyone point me to info on configuring this plugin. I installed it but my job doesn't auto restart.

    I've checked "Rerun Build" , Fixed Delay of 60, "Max number of successive failed build" = 3. I'm running Jenkins in RedHat as a daemon and there is nothing in the log file. Are the parms documented anywhere. This plugin has potential but the abysmal lack of documentation makes it very frustrating. Thanks for any help.

  7. May 31, 2013

    ankurbadola says:

    Anyone can point to how to release newer version? There is no release after 1.8....

    Anyone can point to how to release newer version? There is no release after 1.8. I am interested in this fix:

    • re-schedule limit doesn't consider previous builds that aren't related to naginator
    1. Sep 18, 2013

      oleg_nenashev says:

      Go to the jenkins-dev Google group Ask about the new release If there's no a...
      1. Go to the jenkins-dev Google group
      2. Ask about the new release
      3. If there's no answer, feel free to request committer rights and to release plugin on your own

      Unfortunately, many plugin have not active maintainers... 

  8. Feb 19, 2014

    schleprock says:

    as others have noted, this could be a great plugin but the documentation is awef...

    as others have noted, this could be a great plugin but the documentation is aweful. i'm trying to use the fixed -> delay before retrying parameter and have no idea what the units are for this value. at a minimum it would be nice to add a pop-up to this parameter indicating the units. if anyone knows what the units are, please post!

    schleprock

  9. Apr 10, 2014

    davida2009 says:

    Please update 'Version History' on this page with the changes for versions 1.10 ...

    Please update 'Version History' on this page with the changes for versions 1.10 and 1.11.

    1. Nov 29

      galunto says:

      Done :)

      Done :)

  10. Jul 15, 2014

    sion_oc says:

    Hi, The retry works well but if the job is a triggered with parameters job the ...

    Hi,

    The retry works well but if the job is a triggered with parameters job the Parent caller job will fail (doesnt see its being retried).

    To me this is just a respawn with same parameters functionality. A retry should not have a build result until all the retries are finished. this means that if you set an email on failure wouldnt be triggered until all retries have failed.

    Many Thanks

    Siôn

  11. Feb 22

    jamil_nyc says:

    What are the units of the fixed delay, seconds or minutes?

    What are the units of the fixed delay, seconds or minutes?

    1. Apr 20

      jamil_nyc says:

      It is in seconds if anyone is wondering.

      It is in seconds if anyone is wondering.

  12. Apr 20

    jamil_nyc says:

    It would be great if this plugin worked with the email-ext plugin. Right now, an...

    It would be great if this plugin worked with the email-ext plugin. Right now, any try that fails sends out a failure email and there isn't a clear way to distinguish an automatic retry in the email.

  13. Apr 22

    rnester says:

    This plugin seems to "forget" that it's supposed to be retrying builds. By which...

    This plugin seems to "forget" that it's supposed to be retrying builds. By which I mean the following:

    • I have a job which executes some basic python scripting. 
    • This job is configured to retry the build up to 7 times.
    • This job is configured with a delay of an hour between each retry attempt 

    What I see is that Naginator often seems to "forgets" that it is supposed to be retrying.
    It might rebuild 3, 4, 5 or 6 times, and then no longer reschedule the build in question.

    This seems to be most prevalent when there are multiple builds of the same job occurring simultaneously, although that is very anecdotal.