Instant Data Dictionary
ReleaseManager User Manual
Release Management for Software Development Teams
Control what is in your release at the issue item (or bug ID) level.
When performing a build you can select to exclude issue items and the Release Manager will then exclude all of the changed files that are linked to that issue item.
No more picking through files to try and exclude a set of changes.
A detailed report on issue items and files included in the release is automatically generated.
This allows for targeted and complete testing.
Full traceability on what files were change and why.
The history on why a single file was changed is available as well as the history of each release in general.
Database scripts are automatically combined into a single SQL release file.
This makes deploying the database changes easy as well as making sure that the changes are first saved to your source control system.
You can trigger an automatic build from within the Release Manager application.
You can change variables from within the application which will then be used to control your automated build process.
An example is where you can specify the directory to publish the results to. This allows you to have multiple test sites created from multiple branches running at the same time.
Changed files that are not linked to an issue item are not included in the release.
A branch is auditable and you are given the list of files changed in a branch but not included in the last build.
This is important information to know before you collapse a branch.
The build version and build date can be automatically place in the front-end code and in your database table.
This allows you to display them somewhere in your application so you are always sure of which version of your application you are currently running and if a release has been applied to your application or not.
Samples are included that show how to generate a build at the click of a button.
This allows you to be up and running quickly.
The Release Manager is a web site hosted on your server and your database. It is highly customizable giving you control over how it works in your environment.
How it Works.
When a developer commits his change into Subversion using TortoiseSVN a Release Manager Plug-in pops up. Here he can assign the changed files to a release request or create a new one. If creating a new release request than he also checks which issue items the request is addressing. The list of issue items is pulled from your issue or bug tracking database that you are currently using.
A developer can also create or edit a release request using the Release Manager web application that pulls the file listings from Subversion. Advanced filtering is provided to make this process more efficient.
When it is time to build a release you can enter variables to control the build and select which issue items to build. Only the changed files for those items will be included in the build. An XML file will be generated containing the variables and this file can then automatically trigger a build using Cruise Control or similar tools.
Give it a try, you always have a free one user license.
Overview and Walkthroughs
Release Manager Overview
Creating a Request from TortoiseSVN
Edit Request in the Web Application
4 Minute Video
Doing a Build
7 Minute Video
Release Manager Install and Setup
Northwind Sample Project Setup
3 Minute Video
Northwind Sample Project Demo
Edit a Project
9 Minute Video
TortoiseSVN Plug-in Install and Setup
2 Minute Video
Back To Top
Copyright 2013 ©DigitalTools, LLC. All rights reserved.