Unfortunelty, we cannot use Wikis on a large scale to share information.
A top-down decision says the corporate choice is the QuickPlace, which we happen to dislikeafter giving them a try.
Therefore, we locally use lightweight Wikis, such as the one delivered with FitNesse.
We use CruiseControl to automatically run build scripts upon detection of modifications in the repository.
We track bugs and issues with ClearQuest.
ClearQuest is meant to be coupled to ClearCase, which is a nice feature as version control and issue tracking are such interlinked practices.
Unfortunetly, we use the pair uncoupled!
This is one of these cases when big corporate top-down decisions just don't help ...
Therefore, we violate the "Don't Repeat Yourself" practice as we identify issues and the impacted code in the ClearQuest. Samewise, we identify the impacted code in ClearCase using activities named as the reference of the issue to solve.
After a long legacy of "Build it", my company is now into "Buy it".
It's a real pity, as the best tools are actually free to download thanks to great open-source pojects!
