Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-70073

Naginator plugin does not retry Pipeline jobs

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Not A Defect
    • naginator-plugin
    • None
    • 18.04.1-Ubuntu, Jenkins 2.375

    Description

      After installing the plugin, I could not find the option to check Post-Build action and set the option  "Retry build after failure" on the project's configuration page.

      After installing the plugin, I made a restart "(jenkins_url)/restart" but nothing works out here.

       

      Unfortunately, no log exceptions,

       

      2022-11-13 10:45:32.341+0000 [id=54790] INFO    h.model.UpdateCenter$DownloadJob#run: Starting the installation of naginator on behalf of hari_gudla
      2022-11-13 10:45:32.343+0000 [id=54790] INFO    h.m.UpdateCenter$UpdateCenterConfiguration#download: Downloading naginator
      2022-11-13 10:45:33.781+0000 [id=54790] INFO    h.model.UpdateCenter$DownloadJob#run: Installation successful: naginator

       

       

      Attachments

        Activity

          markewaite Mark Waite added a comment - - edited

          I can't duplicate the problem. Can you provide more details about the steps that you took and the exact plugin versions that are installed on your Jenkins controller?

          Steps that I took while attempting to duplicate the problem:

          1. Install Jenkins 2.375 with the naginator plugin and many other plugins as described in my plugins.txt file
          2. Define a freestyle project (job definition)
          3. Add the post-build action to "Retry build after failure" and save the job definition
          4. Open the job configuration page and confirm that the action is still defined on the job

          My initial suspicion is that one of the installed plugins has a problem with the configuration form modernization that happened in Jenkins 2.277. However, that needs the precise list of plugins and their versions in order to test that theory.

          markewaite Mark Waite added a comment - - edited I can't duplicate the problem. Can you provide more details about the steps that you took and the exact plugin versions that are installed on your Jenkins controller? Steps that I took while attempting to duplicate the problem: Install Jenkins 2.375 with the naginator plugin and many other plugins as described in my plugins.txt file Define a freestyle project ( job definition ) Add the post-build action to "Retry build after failure" and save the job definition Open the job configuration page and confirm that the action is still defined on the job My initial suspicion is that one of the installed plugins has a problem with the configuration form modernization that happened in Jenkins 2.277. However, that needs the precise list of plugins and their versions in order to test that theory.
          hari_gudla Hari added a comment -

          markewaite Seems I missed one more point. Instead freestyle project, I created a "pipeline" project and looking for Post-Build action drop down. Is this plugin more suitable for freestyle projects?

          hari_gudla Hari added a comment - markewaite Seems I missed one more point. Instead freestyle project, I created a "pipeline" project and looking for Post-Build action drop down. Is this plugin more suitable for freestyle projects?
          markewaite Mark Waite added a comment -

          Pipelines are best configured by modifying the Pipeline script rather than modifying the settings through additional plugins available from the job configuration page. That prepares the Pipeline job to store the definition in an SCM system and allow its definition to be managed as part of the SCM history of the repository that it is serving.

          See "Timeouts, retries, and more" in the Jenkins Pipeline documentation for more details.

          markewaite Mark Waite added a comment - Pipelines are best configured by modifying the Pipeline script rather than modifying the settings through additional plugins available from the job configuration page. That prepares the Pipeline job to store the definition in an SCM system and allow its definition to be managed as part of the SCM history of the repository that it is serving. See "Timeouts, retries, and more" in the Jenkins Pipeline documentation for more details.

          People

            Unassigned Unassigned
            hari_gudla Hari
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: