Remote Stop/Kill Command in standalone mode about wiremock

[tomakehurst]

Hi,

Thanks for the feedback!

Two questions:
Is there a reason the @rule approach, or programmatic startup/shutdown inline with your tests isn't suitable?

Have you looked into the option of a Maven mojo that programmatically starts and stops WireMock programmatically? I'm not sure whether there are JVM forking issues with this, but if not then it could be done in very little code and without changing WireMock.

Another tactical approach you could consider is packing WireMock into a WAR (the example-war sub-project in the source shows how to do this) and then running that in Jetty via the Maven plugin.

I agree that some kind of Maven plugin for this might be useful though. I'll add it to the list.

Tom

[rowanhill]

One use case for a REST-based stop command is when using WireMock outside of Java: it's easy enough to start WireMock in standalone mode, but the only way to stop it then is to kill its process. It'd be more elegant to be able to ask WireMock to stop itself - c.f. Selenium's /selenium-server/driver/?cmd=shutDownSeleniumServer URL.

[tomakehurst]

If you've got sufficient access to the remote machine to be able to start it, surely can also kill -3 it?

I've run it this way on a number of projects and these days I tend to wrap it in a unix service so that I can just service wiremock start and service wiremock stop.

Perhaps it's not so simple in under Windows?

[rowanhill]

Yes, you can kill the process (and I suspect you could even manage to do something along those lines in Windows), it just strikes me as being more pleasant (and platform agnostic) to be able to issue a graceful shutdown command.

I've just been having a look into doing this, and it does seem fairly achievable - I won't submit a pull request if you're against it, though. :)

[yogurtearl]

+1, I think this would be useful.

[tomakehurst]

OK, if you're happy to create a PR, I'm happy to merge it.

[tomakehurst]

Released in 1.40