Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

ReleaseDependsSelect 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.

FlexFieldsDependsChange # 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 TicketsDependsIssue 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.

FlexFieldsDependsRollback 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 as read-only.

ReleaseNoSelect 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.

FlexFieldsDependsChange # 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 TicketsDependsOptionally, a ticket for your issue tracking system may be  required.

Package Name

No

Name of the package.

  • If <No Name> is selected, build is initiated without any specific package name.
  • File list will be updated when you select a package, except when selecting <No Name> or newly created package.
  • Package name list will be filtered if Release is selected based on packages configured in Release definition.
  • If you want to add new package, click Plus icon and enter new package name.Package Name can only contain Letters, Numbers, Underscore, Dash, Dot, Space and Parentheses. If you have configured Package Name Script, then new package name will default accordingly.
  • If you want to use existing package, you can just select it from drop-down. If there are too many items in drop-down, you can click + icon and start typing package name in popup, then select specific package, click OK. In this situation, you will be just selecting existing package.

...

During course of development this option is very useful 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 Re-build/Re-deploy/Re-execute icon on project activity screen in the Project Version column. This will bring up corresponding Request Form with stream, flexfields, workflow inputs, and force flag selected per selected 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 using a previous 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. 

...


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.

FlexFieldsDependsChange # 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 TicketsDependsIssue tracking tickets related to the execution.

Workflow Inputs

Depends

Enter values for any inputs that are configured for the deploy workflow.


...