Hello,
I have a pipeline for automated testing of my application.
The action is triggered after each commit. The execution time takes about 10 minutes.
The problem occurs if another commit is performed during these 10 minutes. In this case, the action that is still running is stopped and a new one is started.
Is it possible to configure this so that the working action continues to work, and the action on the second commit either runs in parallel or gets into the queue?
(On the host with runner, the capacity is set to 4 in the configuration)