It seems onedev automatically cancel running job if a new one is trigger by branch update, that's right ?
Why a such behaviour ?
Thanks for you light
Robin Shen commented 9 months ago
Yes, this is by design in order to save resource. For same branch and same job, if a build runs, other builds running on old commits are considered obsolete so gets cancelled.
bufferUnderrun commented 9 months ago
make sense. thanks
bufferUnderrunchanged state to 'Closed'9 months ago
Hi,
It seems onedev automatically cancel running job if a new one is trigger by branch update, that's right ?
Why a such behaviour ?
Thanks for you light