Currently, CCI automagically kills a job when a new job is started on top of it. However, there is no way to trigger any custom actions when the job is killed. In some scenarios, the previous job may have triggered outside actions that also need to be killed (i.e. testing on a third party service such as Saucelabs). It would be great to have the ability to add a custom action/webhook that gets triggered after CCI kills a job. That would allow us to perform cleanup actions such as killing the running third party jobs as well.