http://forge.abcd.harvard.edu/gf/ Gforge Advanced Server RSS Esmond Kane <esmond_kane@harvard.edu>Definitely look at soap or the email integration then: compilation error -> SOAP -> open tracker tkt |-> Email -> open tracker tkt Gregory Sharp <gcsharp@partners.org> The cruise control might work.  I am interested to test it out. Gregory Sharp <gcsharp@partners.org> I can explain how CDash works.  You make the regression tests, and add them to your Makefile (or equivalent).  Whenever your collaborator or end-user builds the package, any compiler errors get transmitted to a CDash server (called the dashboard).  Also, results from regression tests can be sent to the server. As an example, here is a dashboard for Slicer3: http://www.cdash.org/CDash/index.php?project=Slicer3   Esmond Kane <esmond_kane@harvard.edu>GFAS supports Cruise Control (automated Java and dotNet ant build incl. testing). Read more here in Section 10 of the Project Admin Manual: http://forge.abcd.harvard.edu/gf/download/docmanfileversion/66/351/GFAS_Project_Admin_Manual_5.4.pdf We don't have Cruise Control/Tinderbox enabled (this would be the first request). Let me know if you are interested. FWIW the cdash sample files look like a mash of build reports and the tracker/bugzilla. You _may_ be able to do this yourself within GForge (but it will not be as facile as cdash) Note also that GFAS is fully SOAP enabled so it can integrate with any SOAP enabled app. The Workflow triggers could be used to further integrate the workflow. Norton Allen <allen@huarp.harvard.edu>> Greg, Offhand, I don't believe GForge supports any such tools, but I'm curious to know what such support would look like. Do you know what you would hope to see? Gregory Sharp <gcsharp@partners.org> I wonder, does GForge support any software testing/regression tools such as CDash?  (www.cdash.org) Esmond Kane <esmond_kane@harvard.edu>Tracker is based on Bugzilla so it may ease your transition. Another benefit to working with the forge tracker would be just checking the box to make the tracker (only) private. Andrea Goethals <andrea_goethals@harvard.edu>This would be an export from JIRA into Tracker (to move it from a project partner's system into a publicly-accessible Tracker), then potentially an eventual export from Tracker into Bugzilla (to move it back into our non-public in-house system). I haven't used JIRA before so I'm not familiar with its export capabilities. I think it could be made to work (potentially with some custom scripting) but might be easiest for us to go straight from JIRA to Bugzilla for this project. Thanks for all the responses. Esmond Kane <esmond_kane@harvard.edu>Andrea, Does your bugtracker export to a format recognizeable by MSProject? GFAS can import from Project? Similarly: Can you interface with your bugtracker in eclipse? GFAS has an eclipse plugin that may streamline importing bugs? Esmond Norton Allen <allen@huarp.harvard.edu>I certainly don't see any documentation for import or export capability, so yes, I think it would be fairly non-trivial. Esmond Kane <esmond_kane@harvard.edu>This would be non-trivial. Outside of Forge, we would have to scrape your existing db, massage the data and manually import to dump into the gforge database. Norton, am I correct? Andrea Goethals <andrea_goethals@harvard.edu>From reading the gforge end user documentation I think that the answer to my question is no, but wanted to verify this. Is there any way to import bugs into Tracker from another system like Bugzilla, and vice versa?