Home      FAQ      Idea Exchange      Ask a Question      My Stuff      Help   
  
Facility to add a File List to a Bugtrack
As the resolution of a Bugtrack record is progressed, a developer will more than likely have to make a change to a file or files - either as a bugfix to an application file, or as a script to resolve the issue.

At the moment, the only way to record this is to type the filename into the body of the BT along with it's version number. This makes getting the list of files associated with a number of resolved issues difficult, time consuming, and prone to error.

It would be really good if there was the facility to have an updateable file list attached to a BT record header where a developer could add filenames and version numbers for that file.

By having that separate from the body text, it could then be used in an export to create a list of all files and thier version numbers required to release a number of resolved issues.
ID
255
Category
Configuration
Author
Mark Catchpole
Date Created
8/26/2009 5:47:04 AM
Date Updated
9/27/2010 10:17:27 AM
Status
New Idea
Score
20
Promoted By
Caroline BerrieMark Catchpole
Comments
Kirill Bondar  Staff  4/6/2010 11:23:57 AM
If you are using source control system like Visual SourceSafe or CVS/SVN you can integrate it with BUGtrack. When checkin in the file the user could type a issue number in the comment field - the file/version will appear in the Check-ins section on top of the issue.

More information here:
http://www.bugtrack.net/help/#3.6
Mark Catchpole 8/27/2010 9:54:05 AM
We are currently using PVCS - and already add the BT number into the comment when checking in a file. Are there any plans to extend the scope of this facitlity to be able to use it with PVCS?

Thanks
Mark
Kirill Bondar  Staff  8/30/2010 10:40:11 AM
Mark, it depends whether PVCS supports running some sort of script on checkin action. If it does, it would be possible to push the information to BUGtrack.

Unfortunately we have not found neither the documentation nor the way to download trial version of PVCS. If you are familiar with this system we can provide you with the information on BUGtrack's version control system API.
Mark Catchpole 9/16/2010 10:27:28 AM
Kirill, it would be very useful to get some information on the API. I believe PVCS (currently called Serena Version Manager - sorry for the reference to the old name) does support command line, and therefore scripted interfaces. If you could provide me with a link ot download the API documentation, that would be excellent.
Thanks
Mark

Kirill Bondar  Staff  9/27/2010 10:16:51 AM
The integration API is quite simple - when checkin action is triggered you should send an piece of XML to the BUGtrack page.

The XML has the following format:

<cvs>
<record id="<bug-id>" filename="file" oldversion="string" newversion="string"/>
<record id="<bug-id>" filename="file" oldversion="string" newversion="string"/>
...
<record id="<bug-id>" filename="file" oldversion="string" newversion="string"/>
</cvs>

bug-id can be extracted from comment string - we use #nnnnn format to designate bug number.

oldversion and newversion attributes specify previous and new version of the file - this can be used to invoke some diff tool. We use oldversion attribute for integration with Microsoft Visual SourceSave, for CVS/Subversion integration it is always 0.

After XML is formed you should send it via HTTP post request to

https://yoursite.bugtrack.net/cvs.aspx?l=<license-key>

You can find your license-key on License Preferences page.

Feel free to use "#63" and related articles as the reference.
Kirill Bondar  Staff  9/27/2010 10:17:27 AM
Feedback
 
Back to Search Results