...
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. |
Node Executable Path |
| No | An absolute path to a Node executable or its parent directory. If not provided, Node.js must be on PATH. See installNodeJS to install Node.js.If not provided node must be on PATH, or new node can be installed by providing the version in the input 'Nodejs Version'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 'Node Executable Path' |
NPM Install Arguments |
| No | Allows to enter one or more arguments to npm install command. (Ex --no-optional). @Since 6.5.0.14 |
.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/commands/npm-configconfiguring-npm/npmrc |
Project Source Folder |
| No | Path to the folder which contains the application build configuration files (Ex package.json, Gruntfile.js). If a relative path is given, a path inside the FD_TEMP_DIR will be assumed. @Since 6.5.0.19 |
Build Arguments |
| No | Allows to enter one or more arguments to build command. @Since 6.5.0.19 Example, --vx-version='24.07.14632' To use FlexDeploy project version as the extension version, then use it as groovy expression "--vx-version=$FD_PROJECT_VERSION" --force |
Artifacts
This operation produces artifacts that will be stored in the artifacts repository.
...