• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • multijob-plugin
    • None

      When I change the "Quiet period calculator" and save the job config, the value isn't saved, the default "index < 5 ? 0 : 2 * 60" comes back haunting me. I tride to save "0" or "index < 32 ? 0 : 1"

          [JENKINS-62292] Quiet period calculator isn't saved

          John Rocha added a comment -

          This is a critical issue, every time we re-edit a job the quiet period calculator gets reset to the default which clobbers values that were saved before. This needs to be fixed, or back out the quiet period calculator changes.

          John Rocha added a comment - This is a critical issue, every time we re-edit a job the quiet period calculator gets reset to the default which clobbers values that were saved before. This needs to be fixed, or back out the quiet period calculator changes.

          Yes, This is breaking the builds which are triggered. Why is it not being taken as priority?

          Please let us know how to change this default value at-least. Please

          srilakshmi Malla added a comment - Yes, This is breaking the builds which are triggered. Why is it not being taken as priority? Please let us know how to change this default value at-least. Please

          Steve Misky added a comment - - edited

          I've found editing the config.xml for each Parent Multi-Job:

           <quietPeriodGroovy>0</quietPeriodGroovy>

          then "reload from disk"

          is the only way to "fix" this.

          But, each time somebody edits something about the job, the problem returns.

          Steve Misky added a comment - - edited I've found editing the config.xml for each Parent Multi-Job:  <quietPeriodGroovy>0</quietPeriodGroovy> then "reload from disk" is the only way to "fix" this. But, each time somebody edits something about the job, the problem returns.

          John Rocha added a comment -

          Using latest multijob plugin 1.33 and this configuration corruption is still happening. Any ETA on when it will be fixed?

          John Rocha added a comment - Using latest multijob plugin 1.33 and this configuration corruption is still happening. Any ETA on when it will be fixed?

          Jack Frazee added a comment -

          I was having this issue with 1.33

          Just updated to 1.36, and it's now working as expected.

          Jack Frazee added a comment - I was having this issue with 1.33 Just updated to 1.36, and it's now working as expected.

            Unassigned Unassigned
            flocsy Gavriel Fleischer
            Votes:
            7 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: