Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Runs operations to build an Angular2 application. 

Node dependency

This plugin can execute on any endpoint with Node v10.13 or greater.

Inputs

Input Name

Input Code

Required

Description

Node Executable Path

FDNG_INP_NODE_EXE_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'.

Nodejs Version

FDNG_INP_NODE_VERSION

No

Nodejs version. Installs node with the provided version. This input will be ignored if the input 'Node Executable Path' is also provided. @Since 7.0.0.3

Save Artifacts

FDNG_INP_SAVE_ARTIFACTS

Yes

If checked, artifacts will be saved to the Artifacts folder automatically. If you need to perform additional steps on the output, then set this to false and use a copyArtifacts step later in the workflow.

Set to true by default

Output Folder Directory

FDNG_INP_OUTPUT_FILE_LOCATION

No

Specify the output path relative to the project location. By default, the "dist" folder will be used. 

Production Build

FDNG_INP_PRODUCTION

Yes

Should the ng build command be appended with the "--prod" flag. Defaults to true. Leave this as true if this build will eventually be served in a production environment. 

Additional Options

FDNG_INP_ADDITIONAL_OPTIONS

No

Provide any additional arguments to the ng build command. For example --stats-json

NPM Install Arguments

FDNG_INP_NPM_INSTALL_ARGUMENTS

No

Allows to enter one or more arguments to npm install command. (Ex --no-optional) @Since 7.0.0.3

Artifacts

This operation produces artifacts if the Save Artifacts input is checked. The generated artifact file(s) are automatically copied to artifacts folder and subsequently uploaded to artifact repository.

Endpoint Selection

This operation delegates endpoint selection to the workflow developer. The workflow editor will default the selection to "All", which selects all available endpoints associated to the target. Selecting a specific resource will result in selection of endpoints associated to the target which have that resource defined. 

Endpoint Execution

This operation delegates endpoint execution to the workflow developer. The workflow editor will default to "Any", which will execute on a single random endpoint from the selected endpoints.
Changing this value to "All" to will result in execution on all selected endpoints.

Special Considerations

AngularJS

This plugin builds Angular2 applications. AngularJS is not supported

  • No labels