What Signal Does Bitbucket Pipelines Send to a Step When a Pipeline is Stopped?

[Johnathan Gilday]

When a Pipeline is running, and a user requests that it be stopped, what exactly happens to any steps that are currently running? Do they receive a SIGINT? A SIGKILL? Is there a grace period before a SIGKILL? Is it configurable?

[Patrik S · Accepted solution]

Hello @Johnathan Gilday ,

When a pipeline is stopped, either by the API or UI, the running step will be stopped, and the running processes within that step will be forcefully killed, like a kill -9 command, where it sends a SIGKILL to the processes and forces them to terminate.

Hope that helps to address your question.

Thank you, @Johnathan Gilday .

Kind Regards,

Patrik S

[Cyril Moutenet]

It's a shame that initially it was a kill -15 (SIGTERM) before finally sending a SIG kill.
Another possibility is to add a property after-stop called when ‘stop’ is called.

[Eduardo Asenjo]

I've never tried this before, but I wonder if the `after-script` is called on STOP as well or not.

https://support.atlassian.com/bitbucket-cloud/docs/configure-bitbucket-pipelinesyml/#after-script