Fortress Development Blog

[jeremy_sg]

One of the goals of the Fortress 1.1 development cycle is to increasing the opportunities for customers to see what's coming and have early input into features. If you're interested in following the progress, please go over to http://vaultblog.sourcegear.com

You can subscribe to the rss feed at: http://vaultblog.sourcegear.com/xml/rss20/feed.xml

[birdbuster]

I would like to be able to have Cruise Control .Net be able to run after I have checked in a file to fortress, so i would like fortress to somehow call CCNet. Does anybody know if that is possible ?

[jeremy_sg]

You should start by setting up CC.Net and installing the Fortress CC.Net plugin from:

http://www.sourcegear.com/fortress/downloads.html

To configure CC.Net to check a Fortress server for changes, look at:

http://confluence.public.thoughtworks.o ... trol+Block

Set the type to "fortressplugin" to connect to a Fortress server.

Inside the Fortress CC.Net plugin zip, there's a Readme file with instructions and a configuration example for the Fortress Item Comment Publisher. The Fortress Item Comment Publisher will look at any new Source Control transactions included in the build and add a comment to the referenced bugs stating "This bug is referenced by build 1.1.2.XXX", to help you keep track of which builds fix which bugs.