Imperative and dependency based workflows
Registered by
Renat Akhmerov
We need to allow only one style of workflow in Mistral: either fully imperative (using on-success, on-error, on-finish) or purely dependency based. Having this separation it will be much easier to design and analyse workflows and given that we can use cross-workflow references we'll be able to link both types of workflows to design something complicated.
Blueprint information
- Status:
- Complete
- Approver:
- Renat Akhmerov
- Priority:
- High
- Drafter:
- Renat Akhmerov
- Direction:
- Approved
- Assignee:
- Renat Akhmerov
- Definition:
- New
- Series goal:
- Accepted for juno
- Implementation:
-
Implemented
- Milestone target:
-
0.1
- Started by
- Renat Akhmerov
- Completed by
- Renat Akhmerov
Related branches
Related bugs
Sprints
Whiteboard
(?)
Work Items
Dependency tree

* Blueprints in grey have been implemented.