Skip to content

Virtual jobs does not respect blockedBy #3455

@rudra5

Description

@rudra5

What happened: Virtual jobs continue deployment even if there are jobs in blockedBy section that are running.

What you expected to happen: Virtual jobs should not run until all jobs in the blockedBy section have completed.

How to reproduce it: Create a virtual job (job A) with job B in the blockedBy section. Run the pipeline and while job B is executing try running job A in another pipeline. It will succeed when the expected behavior is for it to be blocked until job B completes.

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