...
The Application Activity identifies all build and deployment requests along with the execution status for each request, whether completed/failed or in progress. The Request Status column provides details pertaining to the build or deployment request that was submitted. The table below describes the status lifecycle of an application request.
Object Type | Status | Description | |
|---|---|---|---|
Application Request | Initiated | The initial status that a request receives when it has first been submitted. | |
Pending Approval | Indicates that one or more approvals are required before the request will be sent for execution. | ||
Scheduled | Indicates that the request has been scheduled for execution at some time in the future. | ||
Rejected | Indicates that an approval task or scheduled task for the request has been rejected/cancelled. | ||
| Aborted | The request was aborted by the user for one or more of the projects in the application. | ||
Ready | Indicates that request is has received any required approvals or reached any scheduled time and is ready to begin execution. | ||
| Completed | The request has successfully executed. | ||
| Failed | The request failed for one or more of the projects in the application. |
| Anchor | ||||
|---|---|---|---|---|
|
...
Enter values in the Build Request Form as described in the table below.
Field | Required | Description |
|---|---|---|
Environment | Yes | The environment to execute the build on. |
Force Build | No | If selected, this option forces the build even though no changes detected in the source. By default you can only build if there is any change from last build. Currently this option only appears when a SCM is configured on Project Configuration. |
Stream | Yes | Select Stream for each project. Defaults to main stream (trunk). You can select any branch stream configured for the project. |
Workflow Inputs | Depends | Enter values for any inputs that are configured for the contained projects build workflows. |
Click the Submit Request button to submit the build request for this application.
| Anchor | ||||
|---|---|---|---|---|
|
...
Enter values in the Deployment Request Form as described in the table below
Field | Required | Description |
|---|---|---|
Application Version | Yes | The version of the application to submit for deployment. |
Environment | Yes | The environment to execute the deployment on. |
Force Deploy | Yes | Force a deployment to occur even if the application version is already current in the selected environment. Defaults to No. |
Exception To Window | Yes | Indicate that the deployment is being requested to run outside of any defined deployment window, triggering an approval. Defaults to No. |
Stop On Error | Yes | If selected, any projects which are queued within the current application deployment request will not be executed when one or more running projects within the same application deployment request fail. Defaults to No. |
Start Time | No | An optional delayed start time for the deployment. |
FlexFields | Depends | Change # above is an example of a FlexField configured on the Administration Tab. Any FlexFields that are configured for Deploy Request will display here. |
Workflow Inputs | Depends | Enter values for any inputs that are configured for each contained project's deploy workflow. (e.g. RestartAfterDeploy input pictured above). |
...