continuous-integration Questions - FogBugz Knowledge Exchange

Workflow question, continuous integration/testing and Fogbugz?

2012-01-22T23:44:57Z

At work we use TeamCity to continuously deploy new versions of our software for testing.

If I resolve a case as fixed, and is using the integrated Kiln system, linking commits and cases, is there a way for me to easily identify whether the version I'm currently running has the fix or not?

I could add the change set hash to the built version, but having the hash, can I query directly for cases that are open, ready for testing (assume I'm using a tag for this), and most important of all, part of the version I'm running (ie all the commits for the case are the same as, or ancestors of the changeset the program aw built from)

For instance, there could be a delay from a commit/set case fixed to the actual build running and deploying. I'd like to avoid getting "still not fixed" replies on the case because the fix isn't yet present in the version running on the server.

FogBugz TeamCity issue tracker

2011-02-28T20:29:20Z

I've just released the first version of the FogBugz TeamCity issue tracker plugin.

It works with TeamCity 6

To install the plugin just download fogbugz.zip from https://bitbucket.org/rasmusjp/fogbugz-teamcity/downloads and copy the zip file into the TeamCityData/plugins directory

To configure the plugin follow the instructions at http://confluence.jetbrains.net/display/TCD6/Integrating+TeamCity+with+Issue+Tracker

Has anyone managed to successfully integrate FogBugz with TeamCity?

2010-05-12T13:17:42Z

We're currently considering switching our Continuous Integration from CruiseControl.NET to either Cruise or TeamCity but have discovered that currently TeamCity has no support for FogBugz.

The free version of TeamCity looks awesome and is certainly looking like an alternative to Cruise/CruiseContro.NET. However the lack of FogBugz integration is annoying!

The TeamCity website says that it is possible to integrate with unsupported bug tracking software by adding the correct pattern to the comment-transformation block (in {path_to_teamcity_data_folder}/BuildServer/main-config.xml file) but i'm not sure how to get this to work.

Is there anyone out there who has successfully integrated FogBugz with TeamCity who would be able to help?

Scrum: capturing sprint and build information

2010-02-07T04:42:51Z

I am trying model how we are going to use Scrum in FogBugz and combine this with logging build numbers from nightly builds etc. I have been looking at the implementation from Daniel Root http://www.danielroot.info/2009/08/how-to-apply-scrum-using-fogbugz-7.html. I would like a way testers and users can easily filter to see what issues or features have been addressed from the previous day's work.

So if we use milestones to identity a sprint, how would we identify a specific build in which a feature or bug was addressed? Could we should we use Tags? Perhaps we could create and field using the Custom Field plugin called Build Number? The issue seems that in FB milestone includes the notion of 'Fix For' a nightly build number, a slightly larger sprint, and even a next release product version.

A little more analysis has it that: A product version will be the result of one or more sprints (so a parent-child type relationship) An incrementing build number may well fall in this category as well, but I don't think changing the milestone after every build makes sense?

Does anyone have any experience with this and could shed some light or offer suggestions.

TIA