Skip to content

Concurrency handling and locking #3

Open
@rafi

Description

@rafi

Expect the possibility of a scenario where 2 requests to the same playbook have been made, prevent them from both running of course.

Some CI apps use the "Quiet period" to wait for N-seconds in case another trigger is incoming (pull request/branch change/chat/etc).

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions