Releasing from TFS to production is now possible
InRelease leverages the TFS integration platform to support multiple release scenarios from TFS and provide a complete release solution.
|
|
| Release an existing application version |
|
When InRelease users want to release an existing version of an application, they simply select the version they want and InRelease will offer all the available builds for each components of the application for them to pick from. Then, they just hit the release button. This scenario is often triggered by developers or testers who want to refresh their environments with the latest stable version.
|
| Build and release an application version using a label |
|
This scenario is performed similarly to releasing an existing build. The main difference is that instead of picking a build to release, the user actually picks a label that the developers have applied to the code in TFS source control. InRelease then triggers Team Build to execute the appropriate build operation and releases the result.
|
|
Continuous deployment & daily smoke tests
|
|
InRelease includes a build action that can be added to build definitions (in TFS Team Build) that allows a Release to be automatically created when the build is executed. Team Build allows multiple build definitions per application. InRelease users can choose to release at every check-in, for continuous deployment, have a daily release to easily implement daily smoke tests or to release on-demand using a manual build as the trigger.
|
|
Assemble applications from many TFS Servers
|
|
InRelease allows users to define multiple connections to TFS. Individual components can come from different servers, offering better support for distributed teams.
|
|
Leverage TFS groups in InRelease
|
|
InRelease allows group approvals at any stage in a release cycle. InRelease allows the users to inherit the membership of a TFS group as part of an InRelease group, removing the need to maintain security two places if the groups are used in both systems.
|