Steps marked with alwaysRun get killed immediately if the build is cancelled
Open
- Dominant language
- Python
- Stars
- 5.5k
- Forks
- 1.7k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 6
Description
So, if I have two steps (1 and 2) and step 2 is marked as 'alwaysRun', stopping the build on step 1 will still trigger step 2 and wait till it's finished. However if the build is stopped when step 2 is already started, the step gets killed immediately. That seems inconsistent. I suggest not to kill running step if it's marked as alwaysRun or alternatively introduce a new property "dontKillOnConcel" or something like that.
Contributor guide
Assessment
This issue has not been assessed yet.