Pivotal Tracker integration with CloudForge


CloudForge provides a commit integration with Pivotal Tracker based on our svn or cvs commit hooks. What this means is that when a user commits to a repository, and that repository is in a CloudForge project together with a Basecamp service, the user/developer can update Stories, Bugs, etc in Pivotal Tracker straight from the commit


Configure CloudForge

To configure CloudForge to integrate with Pivotal Tracker, do the following:

As an Admin login to CloudForge and create a project with both SVN and Pivotal Tracker services selected.

Enter your Pivotal Tracker Username and Password.
(Click Test Login to test it > if test successful: click Save)



Integrating your commit - Syntax

The supported actions are to comment on or close ("Finish") a Pivotal story. This is done by using a special syntax in the commit message using Ticket Integration

Here are examples using Ticket Integration Syntax for Pivotal:

svn commit -m "this is my message close[t:7558653]"

(If your CloudForge project has additional Tracking services (like TRAC or Bugzilla), you will need to specify Pivotal like this:

 svn commit -m "this is my message close[s:pivotal, t:7558653]"

For Example...

Let's say you have a story (feature) request in Pivotal... First take note of the Story ID 7558653





Then after you code away part of this feature, you'd like to commit to the repo.... and of course you can also update the story right from the commit: (here shown using Eclipse)




That's it... your Pivotal story gets automatically updated:




You can also "Finish" the Story and it setup for "Delivery" by adding a 'close' action to the syntax ie:

Icons are fully synced now close[t:7558653,s:pivotal]






Article is closed for comments.