Skip to content

Cluster scheduling #3

@mjtko

Description

@mjtko

With the changes outlined in #2 the number of clusters allocated each day will begin to be based on the number of people from each team selected to conduct tests.

Clusters should be allocated in a similar fair way to team members -- each cluster should have been checked once before a cluster may be selected for checking again, e.g. with the following clusters:

Apex
Nova
Flux
Bolt
Pulse
Zenith
Forge

And with 3 people allocated each day, an example schedule could be:

Monday: Nova, Bolt, Flux
Tuesday: Apex, Forge, Pulse
Wednesday: Zenith, Forge (2), Flux (2)
Thursday: Nova (2), Zenith (2), Pulse (2)
Friday: Apex (2), Bolt (2), Nova (2)

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request
    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions