pact_broker 2.11.0 → 2.12.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 2be4a315bf32e66c226b7c5535fc5cab4f946ce7
-  data.tar.gz: 010232f4eb580f069a8894a8c8a0f2186e16824a
+  metadata.gz: d063090dbbc3a73389a38780a8fab42eb34c79ed
+  data.tar.gz: 3e8ad44036962e66ec75ab114fe67f650011a239
 SHA512:
-  metadata.gz: 4090832d24ec979af748a4652423f15f3e4904d0de88ecd66878311973f22d5af10ae87d9a4e8892e3e9f0f172f14cd4203d7c2e3869ea9ad485e34e53a34b6e
-  data.tar.gz: 1598b04e3e30b92706a6435d6bb12209ccd93a92b3129ebfd3394a0f5b29e5f075db7c8aab5b8e9b03e2faa4bc6c322e99b86bcdbe0856c4818bd1dcdcfeb0e2
+  metadata.gz: 06ea287eb052baf4e753222b1c4424f944fa80efaba076cd123ff866a7f1a84d0bcd3b87ce1961fb6586058988b040ab7bd1013e7d0fa9fc78a36dca64fdcbdd
+  data.tar.gz: 34db45d125d6c0921bcfc23918aa6b173e0d3868e5b702511d460f0530e1374be0be185937120e35ac9f1851f3b30f47712a6b8bb83caa02ec624bec60fd8304

data/CHANGELOG.md

@@ -1,3 +1,13 @@
+<a name="v2.12.0"></a>
+### v2.12.0 (2017-11-29)
+
+#### Features
+* changed date published to time ago in words, with full date as mouseover (#145) ([b28f9c3](/../../commit/b28f9c3))
+
+#### Bug Fixes
+
+* fixed issue that caused uninitialized constant PactBroker::Api::Resources::BaseResource (NameError) when running pact_broker with passenger..	 ([0b21a62](/../../commit/0b21a62))
+
 <a name="v2.10.0"></a>
 ### v2.10.0 (2017-11-11)
 

data/README.md

@@ -6,28 +6,34 @@
  [![Issue Count](https://codeclimate.com/github/pact-foundation/pact_broker/badges/issue_count.svg)](https://codeclimate.com/github/pact-foundation/pact_broker)
  [![Dependency Status](https://gemnasium.com/badges/github.com/pact-foundation/pact_broker.svg)](https://gemnasium.com/github.com/pact-foundation/pact_broker)
 
-The Pact Broker provides a repository for consumer driven contracts created using the pact gem.
+The Pact Broker is an application for sharing for consumer driven contracts. It is optimised for use with "pacts" (contracts created by the [Pact][pact-docs] framework), but can be used for any type of contract that can be serialized to JSON.
+
 
 It:
 
-* solves the problem of how to share pacts between consumer and provider projects
-* allows you to [decouple your service release cycles][decouple]
-* provides API documentation that is guaranteed to be up-to date
+* allows you to release customer value quickly and confidently by [deploying your services independently][decouple] and avoiding the bottleneck of integration tests
+* solves the problem of how to share contracts and verification results between consumer and provider projects
+* tells you which versions of your applications can be deployed safely together
+* automatically versions your contracts
+* allows you to ensure backwards compatibility between multiple consumer and provider versions (eg. in a mobile or multi-tenant environment)
+* provides API documentation of your applications that is guaranteed to be up-to date
 * shows you real examples of how your services interact
 * allows you to visualise the relationships between your services
 
 Features:
 
 * A RESTful API for publishing and retrieving pacts.
-* An embedded HAL browser for navigating the API.
+* An embedded API browser for navigating the API.
 * Autogenerated documentation for each pact.
 * Dynamically generated network diagrams so you can visualise your microservice network.
 * Displays provider verificaton results so you know if you can deploy safely.
+* Provides a "matrix" of compatible consumer and provider versions, so you know which versions can be safely deployed together.
 * Provides badges to display pact verification statuses in your READMEs.
-* Enables a pact version to be tagged (ie. "prod") so a provider can verify itself against a fixed version of a pact to ensure backwards compatibility.
-* Provides webhooks to trigger a provider build when a consumer publishes a change to a pact.
+* Enables an application version to be tagged (ie. "prod", "feat/customer-preferences") to allow repository-like workflows. 
+* Provides webhooks to trigger actions when pacts change eg. run provider build, notify a Slack channel.
 * View diffs between Pact versions so you can tell what expectations have changed.
 * [Docker Pact Broker][docker]
+* A [CLI][cli] for encorporating the Pact workflow into your continuous integration process.
 
 ### How would I use the Pact Broker?
 
@@ -42,10 +48,17 @@ Features:
 1. The provider has a verification task that is configured with the URL to retrieve the latest pact between itself and the consumer. eg `http://my-pact-broker/pacts/provider/Animal%20Service/consumer/Zoo%20App/latest`.
 2. The provider build runs the pact verification task, which retrieves the pact from the Pact Broker, replays each request against the provider, and checks that the responses match the expected responses.
 3. If the pact verification fails, the build fails. The [Pact Broker CI Nerf Gun][nerf] magically determines who caused the verification to fail, and shoots them.
-4. The results of the verification are published back to the Pact Broker by the pact verification tool, so the consumer team will know if the code they have written will work IRL.
+4. The results of the verification are published back to the Pact Broker by the pact verification tool, so the consumer team will know if the code they have written will work in real life.
 
 If you don't have a [Pact Broker CI Nerf Gun][nerf], you'll probably want to read about using pact when the consumer and provider are being written by [different teams][different-teams].
 
+#### Step 3. Back to the Consumer CI build
+
+The following funcationality is in beta release. Your feedback would be appreciated.
+
+1. The Consumer CI determines if the pact has been verified by running `pact-broker can-i-deploy --pacticipant CONSUMER_NAME --version CONSUMER_VERSION ...` (see documentation [here](https://github.com/pact-foundation/pact_broker-client#can-i-deploy))
+1. If the pact has been verified, the deployment can proceed.
+
 ## Documentation
 
 See the [wiki][wiki] for documentation on the Pact Broker.
@@ -142,3 +155,5 @@ Please read the [UPGRADING.md](UPGRADING.md) documentation before upgrading your
 [twitter]: https://twitter.com/pact_up
 [gitter]: https://gitter.im/realestate-com-au/pact
 [issues]: https://github.com/pact-foundation/pact_broker/issues
+[pact-docs]: http://docs.pact.io
+[cli]: https://github.com/pact-foundation/pact-ruby-standalone/releases

data/lib/pact_broker/api/renderers/html_pact_renderer.rb

@@ -57,8 +57,8 @@ module PactBroker
                 <span class='value'>#{@pact.consumer_version_number}#{tags}</span>
               </li>
               <li>
-                <span class='name'>Date published:</span>
-                <span class='value'>#{published_date}</span>
+                <span class='name' title='#{published_date}'>Date published:</span>
+                <span class='value' title='#{published_date}'>#{published_date_in_words}</span>
               </li>
               <li>
                 <a href=\"#{json_url}\">View in API Browser</a>
@@ -108,6 +108,10 @@ module PactBroker
           @pact.created_at.to_time.localtime.to_datetime.strftime("%a %d %b %Y, %l:%M%P %:z")
         end
 
+        def published_date_in_words
+          PactBroker::DateHelper.distance_of_time_in_words(@pact.created_at.to_time, DateTime.now) + " ago"
+        end
+
         def json_url
           PactBroker::Api::PactBrokerUrls.hal_browser_url pact_url
         end

data/lib/pact_broker/api/resources/version.rb

@@ -1,5 +1,6 @@
 require 'pact_broker/services'
 require 'pact_broker/api/decorators/version_decorator'
+require 'pact_broker/api/resources/base_resource'
 
 module PactBroker
   module Api

data/lib/pact_broker/doc/views/publish-verification-results.markdown

@@ -2,9 +2,8 @@
 
 Allowed methods: POST
 
-Use the `pb:publish-verification-results` link in the pact resource to publish the result (either success or failure) of a pact verification. The body of the request must include the success (true or false) and the provider application version that the pact was verified against. It may also include the build URL to facilitate debugging when failures occur.
-
-    POST http://broker/pacts/provider/Foo/consumer/Bar/pact-version/1234
+Use a `POST` request to the `pb:publish-verification-results` link (`$['_links']['pb:publish-verification-results']['href']`) in the pact resource to publish the result (either success or failure) of a pact verification. The body of the request must include the success (true or false) and the provider application version that the pact was verified against. It may also include the build URL to facilitate debugging when failures occur.
+ 
     {
       "success": true,
       "providerApplicationVersion": "4.5.6",

data/lib/pact_broker/version.rb

@@ -1,3 +1,3 @@
 module PactBroker
-  VERSION = '2.11.0'
+  VERSION = '2.12.0'
 end

data/pact_broker.gemspec

@@ -52,4 +52,5 @@ Gem::Specification.new do |gem|
   gem.add_development_dependency 'pg', '~>0.21'
   gem.add_development_dependency 'conventional-changelog', '~>1.3'
   gem.add_development_dependency 'bump', '~> 0.5'
+  gem.add_development_dependency 'timecop', '~> 0.9'
 end

data/spec/lib/pact_broker/api/renderers/html_pact_renderer_spec.rb

@@ -1,5 +1,6 @@
 require 'spec_helper'
 require 'pact_broker/api/renderers/html_pact_renderer'
+require 'timecop'
 
 module PactBroker
   module Api
@@ -10,10 +11,13 @@ module PactBroker
           ENV['BACKUP_TZ'] = ENV['TZ']
           ENV['TZ'] = "Australia/Melbourne"
           PactBroker.configuration.enable_public_badge_access = true
+
+          Timecop.freeze(created_at + 3)
         end
 
         after do
           ENV['TZ'] = ENV['BACKUP_TZ']
+          Timecop.return
         end
 
         let(:consumer) { double('consumer', name: 'Consumer')}
@@ -47,6 +51,7 @@ module PactBroker
             expect(subject).to match /<h\d>.*Some Provider/
             expect(subject).to include("Date published:")
             expect(subject).to include("Thu 27 Feb 2014, 11:00am +11:00")
+            expect(subject).to include("3 days ago")
             expect(subject).to match /title.*Pact between Consumer and Provider/
             expect(subject).to match /prod, master/
           end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: pact_broker
 version: !ruby/object:Gem::Version
-  version: 2.11.0
+  version: 2.12.0
 platform: ruby
 authors:
 - Bethany Skurrie
@@ -10,7 +10,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-11-11 00:00:00.000000000 Z
+date: 2017-12-09 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: httparty
@@ -444,6 +444,20 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '0.5'
+- !ruby/object:Gem::Dependency
+  name: timecop
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '0.9'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '0.9'
 description: A server that stores and returns pact files generated by the pact gem.
   It enables head/prod cross testing of the consumer and provider projects.
 email: