Deployment Window Scheduler

At Stripe, teams ship changes to services all the time. To keep production stable, the Service Deployments team runs a scheduler that decides when deployments are allowed.

Time Format and Window Representation

Time is represented as an integer minute_of_week in the range [0, 10079], meaning minutes since Monday 00:00. For example, 0 is Monday 00:00, 60 is Monday 01:00, 1440 is Tuesday 00:00, and 10079 is Sunday 23:59.

Every window is represented as start_minute,end_minute and is half-open: it includes start_minute and excludes end_minute. For example, 10,12 covers minutes 10 and 11.

Implement scheduleDeploymentWindows. The value of part selects one of the following two stages, and inputCsv contains the corresponding CSV rows. Return the resulting deployment windows as [[start, end], ...], sorted by start time.

Part 1: Allowed Windows (Tests 1–4)

A team defines the times of the week when deployments are allowed. During an incident, the Service Deployments team can also define freeze windows that prevent deployments.

A minute is deployable only when it is inside at least one allowed window and inside no freeze window. Compute the week's sorted, continuously deployable windows.

For Part 1, part is "part1", and every row in inputCsv has this format:

start,end,type

The type is either allowed or freeze. Allowed windows may overlap, freeze windows may overlap, and adjacent deployable intervals are returned as one continuous window.

Part 1 Source Example

part1
540,600,allowed
570,585,freeze

The deployable output is [[540,570],[585,600]].

Part 2: Time Zones and Minimum Duration (Tests 5–11)

The scheduler now aggregates windows from teams around the world. Each window may use a different local time zone, but all rows contribute to one global calendar and the result must be returned in UTC.

For Part 2, part is "part2". The first row of inputCsv contains:

utc_now,lead_time_minutes,min_continuous_minutes,k

Each remaining row has this format:

start,end,type,timezone_offset_minutes

The window endpoints are local minute_of_week values for that row's time zone, where local = UTC + timezone_offset_minutes. Convert every window to UTC, normalizing over the 10080-minute week. If a converted interval crosses the weekly boundary, split it at the boundary.

After conversion, a minute is deployable when it is inside at least one allowed window and inside no freeze window. A returned UTC window must:

• start no earlier than utc_now + lead_time_minutes;
• remain continuously deployable for at least min_continuous_minutes;
• end no later than minute 10080.

Clip deployable intervals to the earliest permitted start, discard any remaining interval that is too short, sort the surviving UTC intervals by start time, and return at most the first k. Return fewer than k windows when fewer valid windows exist.