Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move to using the service command with pact-mock-service #41

Merged
merged 1 commit into from
Aug 11, 2017

Conversation

matthewbalvanz-wf
Copy link
Contributor

The start/stop commands in pact-mock-service have trouble with Windows because
it does not exactly support SIGTERM. The simplest solution is to shift how pact-python
runs the mock service to:

  • Start the mock service using the service command
  • Keep track of the subprocess during pact execution
  • Use the terminate options from Python's subprocess module to stop the mock service

@mefellows @jslvtr @bethesque

The start/stop commands in pact-mock-service have trouble with Windows because
it does not exactly support SIGTERM. The simplest solution is to shift how pact-python
runs the mock service to:

- Start the mock service using the `service` command
- Keep track of the subprocess during pact execution
- Use the terminate options from Python's subprocess module to stop the mock service
@matthewbalvanz-wf
Copy link
Contributor Author

This should resolve #39

@mefellows
Copy link
Member

I'm probably going to look at this code to copy/pilfer/... to the NodeJS version. I'll be watching to see how it pans out - great stuff!

@bethesque bethesque mentioned this pull request Jul 30, 2017
@matthewbalvanz-wf matthewbalvanz-wf merged commit edb6c72 into master Aug 11, 2017
@matthewbalvanz-wf matthewbalvanz-wf deleted the fix-running-on-windows branch August 11, 2017 02:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants