The build operation allows for building webMethods packages(source code), whether they are VCS controlled or notSCM(Source control management) managed or checked out directly from webMethods Designer tool( development tool) by the developer. It automatically build builds the code and copy the completed zip file over to the FlexDeploy internal artifact repository. It should be used in build workflows. We need to use SCM-ExportProjectSources plugin flow
It has a dependency on the existing SCM plugins such as cloneProjectSources, extractProjectSources etc to checkout the
...
source code from
...
SCM tools into FlexDeploy TEMP dir
Build is implemented with 2 options as depicted in below.
Environment/Instance Properties
Property Name | Property Code | Required | Description | ||||
|---|---|---|---|---|---|---|---|
webMethods Asset Build Environment exists? | FDWM_ABE_EXISTS | Yes | Used to invoke the corresponding Build flow based on the existence of ABE build script check. | webMethods HOME Dir for (ABE)BUILD ServerBuild Server (ABE) HOME Dir | FDWM_BUILDSERVER_HOME | ONLY IF above property is selected TRUEAssetBuild environment installation home | Used to connect and navigate into webMethods Asset Build Environment-Build Script Path & run the script. |
...
Property Name | Property Code | Required | Description |
|---|
Inputs
| Input Name | Input Code | Required | Description | |
|---|---|---|---|---|
WebMethods Project Path | FDWM_||||
FDWM_PROJECT_NAME | Yes | webMethods project Name (source code) i,e IntegrationServer package name. | ||
| FDWM_PARENT_PROJECT_PATH | No | This is the folder that typically is named for your application and contains your [src] folder. Relative paths are sourced from the FD_TEMP_DIR.No | Parent dir of wm source code (where wm package is located/checked out),do not include wm packageName here. |
Inputs
| Input Name | Input Code | Required | Description |
|---|---|---|---|
Outputs
Output Name | Required | Description |
|---|---|---|
...