Build and Release Management
Rally’s integrations with build applications improve traceability by linking builds to user stories and defect fixes. Build metrics and reports allow teams to improve quality by quickly identifying user stories and defects that are associated with failed builds.
Apache Ant
The Rally Connector for Ant provides your Agile team a helpful indicator to your overall iteration health by creating a link to your build integration tools. Continuous build status is a key quality metric and helps project teams set benchmarks and gauge the progress of their iteration. Rally’s connector with Ant ensures that the status of builds are tagged in dashboards for immediate visibility by all team members.
Cruise Control
Access a centralized view of continuous system quality and build management metrics across the leading open source build tools. The Rally Connector for Continuous Build Integration captures build status from Jenkins, Hudson versions prior to 1.396, Ant and Cruise Control and updates your projects in Rally for full visibility
Jenkins
Access a centralized view of continuous system quality and build management metrics across the leading open source build tools. The Rally Connector for Continuous Build Integration captures build status from Jenkins, Hudson versions prior to 1.396, Ant and Cruise Control and updates your projects in Rally for full visibilityMSBuild
Gain real-time visibility between Rally and Microsoft Visual Studio Team Foundation Server source code assets and build results with seamless integration into Rally’s collaborative Agile planning dashboards. The Rally Connector for Team Build seamlessly links the results of your TFS builds to Rally’s dashboards, providing an instant assessment of your code health with visibility into build status, a key quality metric and benchmark.Scrum Report Spreadsheet
This Ruby code exports an iteration status spreadsheet to Microsoft Excel Format that I have always called a "Scrum Report Spreadsheet." This Scrum Report shows each Rally work item scheduled in an iteration, each task of the work item, and for each day in the iteration how much work is left to do on that task. It is helpful to visualize day-by-day progress and a very common report among scrum teams.
