ExportXMLWordPrintable

    • Type: Bug
    • Resolution: Not A Defect
    • Priority: Blocker
    • Component/s: naginator-plugin
    • Environment:

      Issue description

      The Naginator Plugin has been behaving unexpectedly since Jenkins was upgraded to version 2.555.1.

      The following issues have been observed:

      1. When Fixed delay is selected as the retry delay strategy, the form field for entering the delay value does not appear.
      2. The Retry build after configuration cannot be saved when configuring it on a new job.
      3. For existing jobs that already had the Retry build after option configured, the configuration disappears after the job is saved again.

      The Jenkins logs contain the following error:

       

      {{Received unexpected form data element:

      {"stapler-class":["com.chikli.hudson.plugin.naginator.NaginatorPublisher","com.chikli.hudson.plugin.naginator.ProgressiveDelay"],"$class":["com.chikli.hudson.plugin.naginator.NaginatorPublisher","com.chikli.hudson.plugin.naginator.ProgressiveDelay"],"rerunIfUnstable":false,"delay":\{"value":"0","delay":"","stapler-class":"com.chikli.hudson.plugin.naginator.FixedDelay","$class":"com.chikli.hudson.plugin.naginator.FixedDelay"}

      ,"increment":"","max":"","maxSchedule":"","checkRegexp":false,"regexpForRerun":""}}}

      Expected behaviour

      Selecting Fixed delay should display a field for entering the delay value. The Retry build after configuration should be saved successfully for both new and existing jobs.

      Actual behaviour

      The fixed-delay input field is not displayed, and the retry configuration is either not saved or is removed when an existing job is saved.

            Assignee:
            Nicolas De Loof
            Reporter:
            Sinu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: