...
Column Header | Data Type | Required | Description |
|---|---|---|---|
ProjectName | String | Yes | The name of the project you wish to create |
FolderPath | String | Yes | The folder path to locate the project. Must start with FlexDeploy/ You can use a nested folder structure. The folders will be created, if you have permission to create them. |
Description | String | No | An optional description for the project. |
ProjectType | Enum Values | No | The type of the project you wish to create. If it is left blank in the CSV, a standard project is created. If populated, a Package-Based project will be created of the selected type. You will not be able to change between Standard and Package Based Classifications after upload. The available options are below. Project Type Name or Code to enter in the CSV. EBS - EBS |
DeploySequence | Integer | No | Optionally sets the deploy sequence for the project. |
NextProjectBuildNumber | Integer | No | Optionally sets the next build number for the project. Defaults to 1. |
BranchName | String | No | Optionally sets the branch name for the project. Defaults to the default branch from project defaults. More than one value can be entered separated by comma, in which case double quotes will be required around entire value. Tools like Excel will add the quotes automatically. |
VersionNameSyntax | String | No | Groovy Script Options sets the version name syntax (groovy) for the project. Defaults to the value from project defaults. More than one value can be entered separated by comma, in which case double quotes will be required around entire value. Tools like Excel will add the quotes automatically. |
NextBranchBuildNumber | Integer | No | Optionally sets the next build number for the main branch. Defaults to 1. More than one value can be entered separated by comma, in which case double quotes will be required around entire value. Tools like Excel will add the quotes automatically. |
SparseCheckoutFolders | String | No | Groovy Script Set’s the sparse checkout folder for the project. |
FDGIT_URL | String | Yes (If GIT Code is provided, Code will take priority) | Git URL you would like for the project source. If the URL matches an existing Git Instance, the instance will be used for project creation. If no Git Instance is found, the Git Instance will be required to create the project. If no matching Git instance exists, the current FlexDeploy user will be used to create one. As a result, you may want to assign create/modify integration instance permission to users that you want to create projects in bulk. |
FDGIT_CODE | String | Yes | Git Code for the project source control. If the Code matches an existing Git Instance, the instance will be used for project creation. If Both URL and Code are provided, Code will take priority. If Git instance does not exist for the matching Code, and URL is provided, URL will be considered. If no Git Instance is found, the current FlexDeploy user will be required to create a Git Instance for the project. As a result, you may want to assign create/modify integration instance permission to users that you want to create projects in bulk. |
FDGIT_USER | String | Yes | Git User. This is only required if a Git Instance is not found, and one is being created on project creation. |
FDGIT_PASSWORD | String | Yes | Git Password. This is only required if a Git Instance is not found, and one is being created on project creation. |
BuildWorkflow | String | Yes | The name of the workflow that you wish to use for building the project. A Valid Build Workflow is required in the CSV File in order to upload. Workflow is not editable after upload. |
DeployWorkflow | String | Yes | The name of the workflow that you wish to use for deploying the project. A Valid Deploy Workflow is required in the CSV File in order to upload. Workflow is not editable after upload. |
BuildTargetGroup | String | Yes | The Target Group Code of the target group that you wish to use for builds. Note - this is Code and not Name. |
DeployTargetGroup | String | Yes | The Target Group Code(s) of the target group that you wish to use for deployment. More than one value can be entered separated by comma, in which case double quotes will be required around entire value. Tools like Excel will add the quotes automatically. Note - this is Code and not Name. |
...