This actually turns out to be a feature instead of a bug, steps with execution condition "always execute" will always be executed even if some previous step is cancelled. This is for purpose of doing some cleanup works after cancellation. However current implementation has a bug to cause command steps still being cancelled even if its execute condition is set to "always execute". In QB6 we will make below improvements:
1. Add two step execute conditions "if build is cancelled", and "as long as build is not cancelled".
2. If a step is executed as a cleanup step in case of build cancellation, it can still be cancelled by pressing the cancel button again.
Robin Shen[14/Nov/14 12:51 PM]
This actually turns out to be a feature instead of a bug, steps with execution condition "always execute" will always be executed even if some previous step is cancelled. This is for purpose of doing some cleanup works after cancellation. However current implementation has a bug to cause command steps still being cancelled even if its execute condition is set to "always execute". In QB6 we will make below improvements:
1. Add two step execute conditions "if build is cancelled", and "as long as build is not cancelled".
2. If a step is executed as a cleanup step in case of build cancellation, it can still be cancelled by pressing the cancel button again.
Bug
Resolved
Major
Steps after the cancelled step should not be executed
1. Add two step execute conditions "if build is cancelled", and "as long as build is not cancelled".
2. If a step is executed as a cleanup step in case of build cancellation, it can still be cancelled by pressing the cancel button again.