Doc: explain various combinations of task names and workflow commands work in 'on-xxx' clauses
Bug #1682377 reported by
Renat Akhmerov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Fix Released
|
High
|
Renat Akhmerov |
Bug Description
There maybe various combinations of task names and engine commands in 'on-success', 'on-error', 'on-complete'. For example,
taskA:
action: ...
on-success:
- taskB
- pause
- taskC
or
taskA:
action: ...
on-success:
- taskB
- fail
- taskC
We need to clearly explain how these combinations work in Mistral DSL spec and provide workflow examples illustrating that.
Changed in mistral: | |
milestone: | none → pike-2 |
importance: | Undecided → High |
Changed in mistral: | |
assignee: | nobody → Renat Akhmerov (rakhmerov) |
Changed in mistral: | |
milestone: | pike-2 → pike-3 |
Changed in mistral: | |
milestone: | pike-3 → pike-rc1 |
Changed in mistral: | |
milestone: | pike-rc1 → queens-1 |
Changed in mistral: | |
milestone: | queens-1 → queens-2 |
Changed in mistral: | |
milestone: | queens-2 → queens-3 |
Changed in mistral: | |
milestone: | queens-3 → rocky-1 |
Changed in mistral: | |
milestone: | rocky-1 → rocky-rc2 |
Changed in mistral: | |
milestone: | rocky-rc2 → queens-rc2 |
To post a comment you must log in.
I believe I just ran in to this point of confusion. If a task has 'pause' and after the workflow gets there you set the workflow to "running", is it expected that the other on-success do not execute? This seems to be a different behavior than "pause-before"