search

zalando-incubator / docker-locust

Docker image for the Locust.io open source load testing tool
Other
204 stars 66 forks source link

Abort Jenkins based load test #27

Closed mo-gr closed 7 years ago

mo-gr commented 7 years ago

When running locust as a Jenkins job (as described in the readme), aborting the Jenkins job does not actually abort the running load test.

All the spawned docker containers are still running after the job has been canceled and they still create load.

It would be great, if aborting the Jenkins job would also abort the running load test.

I see three approaches how this could work:

  1. intercept the signal sent from jenkins for aborting and do some cleanup
  2. provide a how-to for a post-build action that does the cleanup if necessary
  3. also spawn a watchdog, that checks if the job is still running and that will cleanup (including itself) after the job has been cancelled

I think, 1. would be the best, and 2. probably the easiest

budtmo commented 7 years ago

Fixed. it will work also for local machine.