This page contains links to additional tools that work with Alcea Fast BugTrack.
<p>
<h2>fbtcmd.pl</h2>
Version: <A HREF="fbtcmd.pl">0.5 - (Aug 17, 2004)</a>
<p>
Commandline tool to interface with Alcea Fast BugTrack.
<p>
This tool uses the Alcea Fast BugTrack SOAP interface to query, create and update issues within the system.  It is built on top of Perl, SOAP::Lite, and optionally Text::ASCIITable.
<p>
<h3>Release notes:</h3>
<p>
This tool is incomplete and should be considered development quality.  Back-up your Fast BugTrack system before using this tool.  There is no warranty that this will work.
<p>
<h3>Syntax:</h3>
fbtcmd.pl &lt;command&gt; &lt;options&gt;<br>
Where &lt;command&gt; is:<br>
getId - retrieve the details of a single bug.<br>
getList - retrieve a list of bugs.<br>
create - create a new bug.<br>
update - update an existing bug.
<p>
&lt;options&gt; are:<br>
TBD

<h3>Examples:</h3>
Retrieve bug 1 details:<br>
fbtcmd.pl getId 1
<p>
Update bug 5 updating the status to "Ready For Retest":<br>
fbtcmd.pl update --mId=5 --mStatus="Ready For Retest" --mDescription="Here is a description..."
<p>
Create a new bug:<br>
fbtcmd.pl create --mSubject="Problem with code" --mAssignedTo="cjustus" --mDescription="There is a problem with the code at line 123... Please investigate immediately" --mStatus=Open --mProject="Project 1"
<p>
Query all bugs assigned to cjustus - retrieving id, subject, and priority:<br>
fbtcmd.pl getList --mAssignedTo=cjustus --mColumn=mId --mColumn=mSubject --mColumn=mPriority
<p>
<h2>cvsupdate.pl</h2>
Version: <A HREF="cvsupdate.pl">0.5 - (Aug 17, 2004)</a>
<p>
Commandline tool to tie cvs loginfo with fbtcmd.pl.
<p>
This tool is called by cvs, parses messages out of the commit log, and updates Alcea Fast BugTrack.  It is dependent on fbtcmd.pl.
<p>
<h3>Release notes:</h3>
<p>
This tool is incomplete and should be considered development quality.  Back-up your Fast BugTrack system before using this tool.  There is no warranty that this will work.
<p>
<h3>Integrating Alcea Fast BugTrack with CVS and CVSWEB.CGI:</h3>
<p>
Alcea has created a set of scripts that allows a developer, when checking in changes to CVS, to enter .bug 123, 456, 789. in the cvs commit comments, which will:<p>
<ul>
<li>Automatically update the specified bugs, adding links to a cvsweb tool as well as the commit comments to the bug description.
<li>Re-assigning the bug (and updating the status as well).
<li>Trigger FBT's notification logic.
</ul>
<b>Note:</b><p>
These scripts are provided without warranty. They are should be considered development quality (vs. production quality) . They will be changing, and will improve over time.  Use at your own risk.
<p>
<b>Requirements:</b>
<p>
On the CVS server:<br>
<ul>
<li>fbtcmd.pl -- a command-line interface to Alcea Fast BugTrack (which in turn requires)
<ul>
<li>Perl
<li>SOAP::Lite
</ul>

<li>cvsupdate.pl -- a perl program which parses cvs commitinfo data, and calls fbtcmd.pl

<li>cvsweb.cgi -- if you want to allow links from Fast BugTrack to a web interface of your CVS installation so that you can quickly view differences in what has been commited.
</ul>
<p>

On your Alcea Fast BugTrack server:
<p>
<ul>
<li>A recent version of Alcea Fast BugTrack (version 4.24 and up)
<li>Soap Enabled (Admin Menu->SOAP . check enable . for security purposes you might want to put the IP address of your CVS server to prevent soap calls from other machines).
</ul>
<p>
Steps:
<p>
<ol>
<li>Ensure that fbtcmd.pl can communicate with Fast BugTrack
<p>
Edit fbtcmd.pl so that SERVICE points to your Fast BugTrack installation.  Test by running:
<p>
fbtcmd.pl getId 1
<p>
You should see the details of bug#1 in your system, in xml format.
<p>
Edit cvsupdate.pl so that it points to the full path to fbtcmd.pl . you will likely want to update the SERVICE variable as well to point to your installation of Fast BugTrack.
<li>Configure your cvs installation so that it is calling cvsupdate.pl, and that cvsupdate.pl is calling fbtcmd.pl
<p>
Check out your CVSROOT module from CVS. (cvs co CVSROOT)
<p>
Edit the file loginfo, adding the following:<br>
DEFAULT (id .un; echo %{sVv}; date; cat) | /usr/local/bin/cvsupdate.pl
<p>
(Note you can replace DEFAULT with a specific CVS module name . this might be handy to run this initially on a module for testing purposes)
<p>
Commit this change.
<p>
<li>Configure Alcea Fast BugTrack to point to your cvsweb location
<p>
In the Fast BugTrack directory . edit the file lang.cfg<br>
Add the following lines:<p>

sCVSWEB,http://cvswebserver/cgi-bin/cvsweb.cgi<br>
sCVSWEBOPT,&f=h
<p>
Where http://cvswebserver/cgi-bin/cvsweb.cgi is the path to your cvsweb.cgi script.

<li>End to end test:
<p>
In a module that is covered by your CVSROOT/loginfo update, make a change and commit . In the comments include .bug 1. in the commit comment. Bug 1 should be reassigned to the creator, and links to cvsweb should be included in the update.
<p>
<ol>

</td></tr>