The build operation allows for building webMethods packages from source code. Generated artifacts are stored in FlexDeploy internal artifact repository.
...
| Tip |
|---|
It is best practice to match FlexDeploy project name to webMethods package name. |
Blog Posts
- https://flexagon.com/2018/03/cicd-with-webmethods-using-flexdeploy/
- https://flexagon.com/2018/05/manage-webmethods-integrationservers-using-flexdeploy/
Environment/Instance Properties
...
Property Name | Property Code | Required | Description |
|---|---|---|---|
webMethods RunTime Type | FDWM_RUNTIME_TYPE | Yes | Select type of artifacts from IS, TN or IS & TN options. |
WM Parent Project Path | FDWM_PARENT_PROJECT_PATH | No | Parent directory of webMethods source code, do not include webMethods Package Name here. Relative path is assumed to be in workflow execution temp folder. You can provide more than one path using comma(,) separator. This is optional property and can be left empty, in which case plugin will derive location automatically. For Git and CVS parent folder of each extract is considered and for other SCM temp directory is assumed. |
Inputs
| Input Name | Input Code | Required | Description |
|---|---|---|---|
...