Table of Contents |
---|
...
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. |
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. |
...
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. |
...
Build Selected Files option will display the following Build request form and gives option to select one or more files.
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. 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 as 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.
|
...
To remove files from the list of files to be included in the build, select the files and select Remove from the Selected Files drop down.
Clear Selected Revisions
Clears the revisions for the files that are selected, go to the Selected Files drop down and choose Clear Revisions. If revision is not present latest file will be retrieved from source control system.
Entering Revisions
On the Build Request Form, you can add revisions for each file you are building. Currently, these revisions all must be contained by the stream you selected for the build.
You may enter the revision in the text box or click the magnifying glass to look up the revision. When looking up the revision, the following screen will pop up:
...
At times, the order of both build and deploy can be important. You can control the order by the sequence of the files in the list. If you need to alter the order, use the Up Button to move the selected row(s) up one row. If multiple rows are selected, the top row is moved up by 1 row, the remaining selected rows are placed right below the highest selected row. Use the Down Button to move the selected row(s) down one row. If multiple rows are selected, the bottom row is moved down by 1 row, the remaining selected rows are placed right above the lowest selected row. Similarly you can use Top and Bottom to move selected row(s) to top or bottom of list.
Submit Request
Click the Submit Request button to submit the build request.
...
Re-build, Re-deploy, or Re-execute a Workflow Execution
During course of development this option is very useful as to redo a specific Build, Deploy, or Utility execution. In the case of packages, developers will be updating files and refining package over time. You can click Rebuild Package with Same Files Re-build/Re-deploy/Re-execute icon on project activity screen in the Project Version column. This will bring up Build corresponding Request Form with release, stream, flexfields, workflow inputs, package and file with revisions force flag selected as per selected version of package. This helps setup build request quickly. workflow execution. Depending on the workflow execution selected, more fields will be automatically populated such as for package based build where the files will automatically be populated with selected revisions. This helps create new build, deploy, or utility requests quickly based on the current workflow execution's parameters. Now user can add / remove files or change revisions or clear out revision to fetch latest files prior to submitting request.
Info | ||
---|---|---|
| ||
|
...
|
Deploying a Partial Deployment Project
...
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. |
...