FlexDeploy provides Generic project type to implement customized partial deployment for specific type of artifacts. This is only necessary when requirement is to track deployment of individual file. In future, FlexDeploy will provide ability to create specific project type and it's metadata but in meantime Generic project type should be utilized.
Name | Code | Description | Default Value | Supported Values |
---|---|---|---|---|
Source | SOURCE | This is hidden and defaults to SCM | SCM | SCM |
Target Location | TARGET | Target Folder to place the file into. You can ignore this if value is not necessary for deployment. | ||
Attribute 1 | ATTRIBUTE1 | You can ignore this if value is not necessary for deployment. | ||
Attribute 2 | ATTRIBUTE2 | You can ignore this if value is not necessary for deployment. | ||
Attribute 3 | ATTRIBUTE3 | You can ignore this if value is not necessary for deployment. | ||
Attribute 4 | ATTRIBUTE4 | You can ignore this if value is not necessary for deployment. | ||
Attribute 5 | ATTRIBUTE5 | You can ignore this if value is not necessary for deployment. |
Name | Code | Description | Default Value | Supported Values |
---|---|---|---|---|
partialExecute
operations from Unix Shell, Windows Shell and Powershell plugins. Other plugins like File can work with Generic project type, but that is not recommended to avoid confusion on various properties. Plugin SDK is not available for partial deployment operations yet.echo $SOURCE_FILE
. Files are automatically extracted from source control system when build is executed for partial deployment projects.