Update to ruby-standalone 1.8.0 and delegate publishPacts to new pact-publish executable
See original GitHub issue@bethesque commented on Sat Sep 30 2017
The pact-publish command merges pact files for the same consumer/provider (that have been created by running in specs in parallel) before publishing them to the broker.
Usage:
pact-publish PACT_DIRS_OR_FILES ... -a, --consumer-app-version=CONSUMER_APP_VERSION -b, --broker-base-url=BROKER_BASE_URL
Options:
-a, --consumer-app-version=CONSUMER_APP_VERSION # The consumer application version
-b, --broker-base-url=BROKER_BASE_URL # The base URL of the Pact Broker
-n, [--broker-username=BROKER_USERNAME] # Pact Broker basic auth username
-p, [--broker-password=BROKER_PASSWORD] # Pact Broker basic auth password
-t, [--tag=TAG] # Tag name for consumer version. Can be specified multiple times.
-v, [--verbose=VERBOSE] # Verbose output
Publish pacts to a Pact Broker.
@mefellows commented on Mon Oct 16 2017
cc: @mboudreau I assume this needs to go in pact-node?
@mboudreau commented on Mon Oct 16 2017
@mefellows pact-node/pact-standalone, yep.
Issue Analytics
- State:
- Created 6 years ago
- Comments:23 (23 by maintainers)
Top Results From Across the Web
Update to ruby-standalone 1.8.0 and delegate publishPacts to ...
The pact-publish command merges pact files for the same consumer/provider (that have been created by running in specs in parallel) before ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes, we do. It would be a great way to validate moving forward, but right now, I’m just trying to get this over the line with tests that work since I’ve been trying to get the new publish binary working with pact node for a couple weeks, and have more important things to work on, like the website.
I’d love to get to a point where we use our own tech to validate our own work, which would be great when we’re doing major internal changes (pact reference anyone?) While still keeping all the functionality.
We can chat about this further another time, right now, just trying to get the publish binary done and dusted.
On Tue., 7 Nov. 2017, 1:36 pm Beth Skurrie, notifications@github.com wrote:
Awesome, closing this then.