question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

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:closed
  • Created 6 years ago
  • Comments:23 (23 by maintainers)

github_iconTop GitHub Comments

1reaction
mboudreaucommented, Nov 7, 2017

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:

Dude, we need a contract 😛 I can’t guarantee that output won’t change.

— You are receiving this because you were assigned.

Reply to this email directly, view it on GitHub https://github.com/pact-foundation/pact-node/issues/49#issuecomment-342357010, or mute the thread https://github.com/notifications/unsubscribe-auth/AAjA5MWaZ6uanMrte2A6ViCCxksR0ykyks5sz8IWgaJpZM4P78xE .

0reactions
mefellowscommented, Dec 9, 2017

Awesome, closing this then.

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found