automatically reset reserved_slaves

RESOLVED WONTFIX

Status

Release Engineering
Release Automation
P3
normal
RESOLVED WONTFIX
6 years ago
5 years ago

People

(Reporter: bhearsum, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
After update verify runs we should be resetting reserved_slaves automatically. Should be pretty easy to do with a new builder + MasterShellCommand.
(Reporter)

Comment 1

6 years ago
We might want to extend this to automatically _setting_ it at the start of a release too. (Although, ideally you want to set it a few hours in advance)

Comment 2

6 years ago
This may be problematic when two releases run on the same master, with staggered start/end times.
(Reporter)

Comment 3

6 years ago
(In reply to Aki Sasaki [:aki] from comment #2)
> This may be problematic when two releases run on the same master, with
> staggered start/end times.

Good point. Also, low priority.
Priority: -- → P3
(Reporter)

Comment 4

6 years ago
(In reply to Ben Hearsum [:bhearsum] from comment #3)
> (In reply to Aki Sasaki [:aki] from comment #2)
> > This may be problematic when two releases run on the same master, with
> > staggered start/end times.
> 
> Good point. Also, low priority.

Actually, I think you could work around this by using +/- instead of setting an absolute value.
(Reporter)

Comment 5

5 years ago
We don't use reserved slaves in the multimaster world.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.