Build Oracle Visual Builder Applications from source code. Artifacts produced will be optimized.zip (the build to be deployed) and sources.zip (the source code).
This operation expects the source code to be in an unzipped format.
Either FDOVB_CLOUD_ACCOUNT_CODE
Target property value or FDOVB_INP_CLOUD_ACCOUNT_CODE
plugin input value should be configured. When both are set, the plugin input value will take precedence. See Creating/Editing a Cloud Account and Provider for details on how to setup Cloud Account for OVB.
Target Properties
Property Name | Property Code | Required | Description |
---|---|---|---|
Oracle Visual Builder Account |
| No | The OVB account with all the required properties like Base URI, Username and Password for running OVB Instance. |
Inputs
Input Name | Input Code | Required | Description |
---|---|---|---|
Oracle Visual Builder Account |
| No | The OVB account with all the required properties like Base URI, Username and Password for running OVB Instance. |
Skip Optimize |
| No | Skip optimizing the build. |
Mode |
| Yes | Defines the build mode. Value of 'default' builds a visual application's assets for deployment to Visual Builder runtime service. Value of 'fa' builds a visual application's assets for deployment to an Oracle Cloud Applications environment. |
FA Index Html Resolve Variables |
| Yes | When Mode is set to 'fa' and if this property is set to false, the generated index.html does not resolve JET and VB URL and version template variables. The file will contain %JET_CDN_PATH%, etc. |
Enable Telemetry |
| Yes | If true injects the Trace.ConsoleProfile initializer into the generated index.html |
Node Executable Path |
| No | An absolute path to a Node executable or its parent directory. If not given, node in path will be considered. @Since 6.5.0.16 |
Nodejs Version |
| No | Nodejs version. Installs node with the provided version. This input will be ignored if the input |
NPM Install Arguments |
| No | Allows to enter one or more arguments to npm install command. (Ex --no-optional). @Since 6.5.0.13 |
.npmrc |
| No | npm configurations entered as list of key = value parameters (e.g. loglevel=notice), one key value pair per line. @Since 6.5.0.15 All default npmrc configurations are listed when the command “npm config list -l” is run. Some examples are- 1.registry=https://registry.npmjs.org/ (Specifies the URL of the npm registry) 2.strict-ssl=false (Controls SSL certificate validation during HTTPS requests.) 3.proxy=http://your-proxy-url:port 4.loglevel=verbose (Sets the logging level for npm output (e.g., 5.production=true (Instructs npm to skip installation of devDependencies.) For more details, refer npm-config | npm Docs Also, when multiple .npmrc files are available, npm follows a specific hierarchy for merging these configurations. Such as Project-Specific > User-Specific >Global. For more details, refer https://docs.npmjs.com/cli/v10/configuring-npm/npmrc |
Artifacts
This operation produces artifacts that will be stored in the artifacts repository.
Endpoint Selection
This operation will select all available endpoints associated to the Target.
Endpoint Execution
This operation will execute on any one of the selected endpoints and will be random in the determination of which one.