| Table of Contents |
|---|
...
The Project Activity identifies all build and deployment requests along with the execution status for each request, whether completed/failed, pending approval, scheduled or in progress. The Workflow Request columns provides details pertaining to the build or deployment request that was submitted. Once a workflow request begins execution the Workflow Execution columns will provide details pertaining to its execution on the target instance. The Figure below describes the status lifecycle of a workflow request and its workflow execution.
| Tip |
|---|
Project activity is sorted by requested time in descending order. |
Object Type | Status | Description |
|---|---|---|
Workflow 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 workflow execution was aborted by the user for this request. | |
Ready | Indicates that the request has received any required approvals or reached the scheduled time and is ready to begin execution. | |
Submitted | Indicates that the request has been sent for execution. | |
Failed | Indicates that the request has failed. | |
Completed | Indicates that the request has been successfully executed. | |
Workflow Execution | Queued | The initial status when a request is ready for execution. |
Running | Indicates that execution is in progress. | |
| Aborted | The workflow execution was aborted by the user. | |
Failure | Indicates that the execution has failed. | |
Success | Indicates that the execution has completed successfully. |
...
Field | Required | Description |
|---|---|---|
Environment | Yes | The environment to execute the build on. Note that if there is only one environment configured for the build, it will be preselected. |
Instance | Yes | The instance to execute the build on. Note that if there is only one instance configured for the build workflow it is preselected and marked and read-only. |
| Release | Depends | Select the release the build should be associated to if applicable. If a release is selected, the build will create a snapshot for the release. |
Stream | Yes | Select project stream to build from. Defaults to main stream (trunk). You can select any branch stream configured on the Project Configuration screen. |
Force Build | No | If selected, forces the build even though no changes detected in the source. By default only build if there is any change from last build. |
| FlexFields | Depends | Change # above is an example of a FlexField configured on the Administration Tab. Any FlexFields that are configured for a Build Request will display here. |
| Related Tickets | Depends | Issue tracking tickets related to the build. |
Workflow Version Override | No | Optionally select the version of the workflow to execute. Defaults to the active version. Defaults to the active version. |
Workflow Inputs | Depends | Enter values for any inputs that are configured for the build workflow. The workflow itself defines whether each input is required or not. |
| Related Tickets | Depends | Optionally, a ticket for your issue tracking system may be required. |
...
Field | Required | Description |
|---|---|---|
Project Version | Yes | The version of the project to submit for deployment. |
Environment | Yes | The environment to execute the deployment on. |
Deploy Instance(s) | Yes | The instance(s) to execute the deployment on. The list of instances which appear in the list are the deploy instances which are configured for the project. |
Force Deploy | Yes | Force a deployment to occur even if the project 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. |
Start Time | No | An optional delayed start time for the deployment. |
| FlexFields | Depends | Rollback on Failure? above is an example of a FlexField configured on the Administration Tab. Any FlexFields that are configured for Deploy / Utility Request will display here. |
Workflow Version Override | No | Optionally select the version of the workflow to execute. Defaults to the active version. |
Workflow Inputs | Depends | Enter values for any inputs that are configured for the deploy workflow. |
...
Field | Required | Description |
|---|---|---|
Environment | Yes | The environment to execute the build on. Note that if there is only one environment configured for the build, it will be preselected. |
Instance | Yes | The instance to execute the build on. Note that if there is only one instance configured for the build workflow it is preselected and marked and read-only. |
| Release | No | Select the release the build should be associated to, if applicable. If no packages for the project are configured in any Release, release drop down will not be shown. If a release is selected, the build will create a snapshot for the release. |
Stream | Yes | Select project stream to build from. Defaults to main stream (trunk). You can select any branch stream configured on the Project Configuration screen. |
Force Build | No | If selected, forces the build even though no changes detected in the source. By default only build if there is any change from last build. Currently only appears when SVN is selected as SCM Type in Project Configuration. |
| FlexFields | Depends | Change # above is an example of a FlexField configured on the Administration Tab. Any FlexFields that are configured for a Build Request will display here. |
Workflow Version Override | No | Optionally select the version of the workflow to execute. Defaults to the active version. Defaults to the active version. |
Workflow Inputs | Depends | Enter values for any inputs that are configured for the build workflow. The workflow itself defines whether each input is required or not. |
| Related Tickets | Depends | Optionally, a ticket for your issue tracking system may be required. |
Package Name | No | Name of the package.
|
...
Field | Required | Description |
|---|---|---|
Environment | Yes | The environment to execute the deployment on. |
Execute Instance(s) | Yes | The instance(s) to execute the workflow on. The list of instances which appear in the list are the deploy instances which are configured for the project. |
Force Execute | Yes | Alway set to yes. Utility projects will execute every time. |
Exception To Window | Yes | Indicate that the execution is being requested to run outside of any defined execution window, triggering an approval. Defaults to No. |
Start Time | No | An optional delayed start time for the execution. |
| FlexFields | Depends | Change # above is an example of a FlexField configured on the Administration Tab. Any FlexFields that are configured for Deploy / Utility Request will display here. |
Workflow Version Override | No | Optionally select the version of the workflow to execute. Defaults to the active version. |
| Related Tickets | Depends | Issue tracking tickets related to the execution. |
Workflow Inputs | Depends | Enter values for any inputs that are configured for the deploy workflow. |
...