Skip to content

Scaling on Waiting has unexpected behavior #199

@baderbuddy

Description

@baderbuddy

Because every job behind a block is considered waiting, if you turn on scaling based on waiting it could cause a lot of unexpected scaling. In our organization we do a lot of block steps for optional things like rollbacks, that most of hte tiem are never executed, so we have plenty of jobs that are stuck in a waiting stage that never get cleaned up.

Having a little more logic in there to exclude older blocked steps, or jobs behind a block would make this option much more useful.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions