Generates an artifact jar of checked out objects for deployment. You should checkout or export code from SCM prior to running this operation. Checkout or Export can be easily done if you configure project with Source details.
...
As of plugin version 4.6.20, this operation also supports partial build. Partial build creates a build artifact containing file(s) and folder(s) selected on the Project Files tab of a project. When using partial build, the plugin will generate a zip file named {{FD_PROJECT_NAME}}.zip . Note that the structure of this file will match the folder structure from SCM, even if the TARGET attribute is set to a different path. This is so the user can easily change the target and redeploy to MDS to update the file path inside of MDS without having to rebuild the entire project.
Environment/Instance Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Project Properties
| Property Name | Property Code | Required | Description |
|---|---|---|---|
| MDS Base Object Path |
| No | The relative directory path from where MDS objects will be included in artifact. If you want all files from configured Project Sources, then you can leave this property empty. |
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
Outputs
Output Name | Required | Description |
|---|---|---|
Project File Attributes
| Info |
|---|
The following properties are Project File Attributes. They are only available on Partial Deploy projects. |
| Attribute Name | Attribute Code | Required | Description |
|---|---|---|---|
| Target Path | TARGET | Yes | The path in MDS where the file should be placed. Default value is the SCM file path. |
| Property Replacement | PROPERTY_REPLACEMENT | Yes | Weather or not to perform property replacement on individual files. Defaults to the value of FDMDS_PROPERTY_REPLACEMENT. |
...
If your MDS objects are in separate SCM folders, then everything will be easy to build and deploy, but if you have one single SCM folder, but would like to create more than one FlexDeploy projects, you need to utilize MDS Base Object Path and Checkout Folder to control what gets included in artifacts jar file. For example:
Subversion Example
- Subversion Folder structure
/trunk/namespace/order/order.xsd/trunk/namespace/customer/customer.xsd
- If you want both of the objects
- Configure
/trunk/namespaceon Project Source. - No need to set anything for
MDS Base Object Pathand all objects will be included in artifact jar file and it will have proper structure i.e.order/order.xsdandcustomer/customer.xsd. - Configure namespace on Project Properties.
- Configure
- If you want only customer objects
- Make sure you only checkout
/trunk/namespace/customerfolder only as we are only interested in customer objects here. - Use
namespace/customeras checkout folder as we still want to maintain structure of objects. - Set
namespaceasMDS Base Object Path. - So we have only checked out objects necessary for our project, so only customer folder related objects will be included in artifact jar file, but it will still have proper structure, i.e.
customer/customer.xsd.
- Make sure you only checkout
- Configurations for what should be checked out and checkout folder is done on Source Configurations for project and SCM plugins will automatically utilize that information.
Git Example
- Git Folder structure
/MDS/namespace/order/order.xsd/MDS/namespace/customer/customer.xsd
- If you want both of the objects
- Use
/MDSfor sparse checkout folders and empty checkout folder. - Set
/MDS/namespaceasMDS Base Object Path, and all objects will be included in artifact jar file and it will have proper structure i.e.order/order.xsdandcustomer/customer.xsd.
- Use
- If you want only customer objects
- Use
/MDS/namespace/customerfor sparse checkout folders and empty checkout folder. - Set
/MDS/namespaceasMDS Base Object Path. - So we have only checked out objects necessary for our project, so only customer folder related objects will be included in artifact jar file, but it will still have proper structure, i.e.
customer/customer.xsd.
- Use
- Configurations for sparse folder and checkout folder is done on Source Configurations for project and SCM plugins will automatically utilize that information.
...