Quiet period calculator cannot be changed

[dmartell-bp]

The Quiet period calculator has a default of "index < 5 ? 0 : 2 * 60" but cannot be changed. This is a major bug for anyone trying to spin up more than 4 simultaneous test environments using the MultiJob plugin.

[caseyduquettesc]

Luckily, looking at the code, this looks more like a UI bug. You can confirm if you look at your job config history, it saves the values you enter, but when edit the job, it always loads the default value. This unfortunately means you will need to be careful whenever you save the job to always enter a sane value.

Personally, I'll probably go back to 1.32.

[xUrko]

I am still running 1.31 since 1.32 also did not work properly.

[RochaStratovan]

Why is the default value anything other than 0. We've had sizable performance hits due to this default value being applied because of some trivial unrelated edit to the job description. It may be caused by a UI issue, but it's a rather serious issue since it silently changes unrelated values.

[flocsy]

I agree, please set the default value to be 0, that's backwards compatible with how it behaved before the quietPeriodCalculator was added.

[RochaStratovan]

Any idea on when this critical defect will be fixed?

[srilakalways]

I agree, please set the default value to be 0, that's backwards compatible with how it behaved before the quietPeriodCalculator was added.

Where can the value be changed globally?

[anoymouserver]

should be fixed with #201

[RochaStratovan]

Do we know when this will be released? I have latest 1.33 and I still see this issue.

[ccnet-microarea]

Do we know when this will be released? I have latest 1.33 and I still see this issue.

Me too! That's the reason because I had to downgrade to 1.32, but 1.32 has the Next phase is EXECUTING even though the previous phase is FAILED issue, which is pretty critical for us...

[RochaStratovan]

Do we know when this will be released? I have 1.33 and I still see this issue. This is a configuration corruption. A value unrelated to what we are editing is being changed, and it causes problems.

[naqushab]

Any update on the fix? Is there a workaround to this?

[yorammi]

We released 1.36 (at last - we have odd authentication issues with jenkins-CI) and it includes a fix for this issue.