Deployment includes all the activities that make a software system or application available for use in an environment, including the physical movement of files, execution of commands, and configuration of environment settings.
Deployment in Serena Release Control is done at the release package level. Release packages are deployed when they reach the state in the lifecycle in which deployment is initiated. In the default workflow, this state is reached when the Deploy action is requested.
The deployment tasks associated with a release package stage are executed when you deploy the release package to that stage. The default release package workflow is shown in Actioning Release Packages Through the Workflow.
|
|
|
NOTE Depending on your organization’s processes you may be able to deploy the release package independently of an application release, or you may be required to associate the release package to an application release before you deploy it. |
To deploy a release package:
Select a release package that is in a state that is ready to deploy.
Click Deploy.
The release package is deployed and installed into the first stage deployment area. Since this is a major release, the first stage is INT.
This is where integration testing takes place. When the testing is completed, the release is ready to deploy to the next stage.
Upon successful execution, vault and automation deployment tasks move into the Completed state. Manual deployment tasks must be moved into Completed or Failed state by the task owner through the associated user interface actions.
If a vault or automation deployment task process fails for any reason during execution, the deployment task moves into the Failed state and is listed in the current owner’s inbox, where the owner can take corrective action.