Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Persistent integration from Lighthouse to Pivotal

branch: master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 bin
Octocat-spinner-32 config
Octocat-spinner-32 lib
Octocat-spinner-32 .gitignore
Octocat-spinner-32 .rvmrc
Octocat-spinner-32 Gemfile
Octocat-spinner-32 Gemfile.lock
Octocat-spinner-32 MIT.LICENSE
Octocat-spinner-32 README.rdoc
Octocat-spinner-32 VERSION
README.rdoc

PivotHouse

A Lighthouse to Pivotal bridge

Setup

You will need to generate token with both Read and Write permissions at Lighthouse.

You will need to create a dedicated user on PivotalTracker, this user should only be used for the purposes of this integration.

Copy the file config/config.example.yml to config/config.yml

Modify the config/config.yml to match your environment. Unfortunately there are a lot of required fields and the error handling is not very robust.

Register the callback with Lighthouse using 'bin/pivothouse register'

Start the server using 'bin/pivothouse start'

Design considerations

  • Uses both Lighthouse and PivotalTracker REST APIs directly (not using a specific API gem)

    • There are ruby gems for access to Lighthouse, these are almost all designed around pushing data into Lighthouse. This application needs to use Lighthouse callbacks and consequently had to do much of the functionality internally.

    • There are ruby gems for access to PivotalTracker, but there are some bugs preventing some behavior.

  • Handle the echos between the two systems is one of the more complex parts of this integration, and its still incomplete (Lighthouse still gets an echo from PivotalTracker).

Something went wrong with that request. Please try again.