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 9 Next »

Executes a Grunt file using the given inputs as parameters. You can specify which gruntfile, tasks and targets, additional parameters. See installNodeJS to install node prior to execution of this operation.

Inputs

Input NameInput CodeRequiredDescription
Node Executable PathFDGRUNT_INP_NODE_EXE_PATHNoAn absolute path to a Node executable(grunt and grunt-cli package must be installed). If not provided node must be on PATH.
Working DirectoryFDGRUNT_INP_WORKING_DIRECTORYNo

The working directory where the Grunt commands will be executed. This path can be relative or absolute. If relative the path will be relative to the temp directory. If not provided directory containing package.json will be used.

Grunt FileFDGRUNT_INP_GRUNT_FILENoAbsolute or relative path to Grunt file. Relative path will be considered inside working directory. If not provided this value will be defaulted to gruntfile.js.
TasksFDGRUNT_INP_TASKSNoComma separated list of grunt tasks to run. If not provided the default task will run. You can specify targets with Task:Target.
Additional ParametersFDGRUNT_INP_ADDITIONAL_PARAMETERSNo

Additional arguments to pass to Grunt. For example, --force, --verbose, or --stack. The Grunt file parameter (--gruntfile) is not required as it is handled with Grunt File input. This input will be appended to the grunt command as it is entered.

Artifacts to SaveFDGRUNT_INP_ARTIFACTS_TO_SAVENo

A relative path to a directory to save as an artifact. This path will be relative to the working directory. If not provided no artifacts will be saved. Use '.' notation to save the entire working directory.

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 environment/instance.

Endpoint Execution

This operation will execute on any one of the selected endpoints and will be random in the determination of which one.

  • No labels