Grunt Action
The Grunt action in Continua is a wrapper around the Grunt command line. If you're having trouble using the Grunt action, please refer to the Grunt Command Line Reference.
The Grunt action is used to run node.js tasks specified in a Gruntfile.
Grunt
Name
A friendly name for this action (will be displayed in the actions workflow area).
Enabled
Determines if this action will be run within the relevant stage.
Grunt File
The path and file name of the Grunt file which defines the tasks to run. Leave blank to use the gruntfile.js file located in Base Path. [---gruntfile]
Base Path
An alternate base path. By default, all file paths are relative to the Grunt File. [---base]
Tasks
A space separated list of tasks to run. Leave this black to run all tasks.
Task Directories
Additional directory paths to scan for tasks and task related files. Relative paths will be anchored to the workspace folder. [---tasks]
Using
The Using drop down is populated with any property collector whose namespace matches the pattern defined by the Grunt action. The pattern for this action is ^Grunt.*
If you create a property collector for this action, make sure you select the Path Finder PlugIn type and give it a name that will match the pattern above in blue. Example names listed here, search the table's Plugin column for "Grunt".
For more in-depth explanations on property collectors see Property Collectors.
Alternatively, you can select the Custom option from the Using drop down list and specify a path in the resulting input field that will be displayed. Please read Why it's a good idea to use a property collector before using this option.
Settings
NPM PlugIns
Names of Grunt plugins to load tasks form. These plugins must be installed locally via NPM, and must be relative to the Gruntfile.
Variables
Additional variables to pass to your Grunt script. Specify one name and value pair per line.
Pre-install Grunt to base path using NPM
Grunt needs to be installed the the base path before the tasks can be run. Tick this to automatically install Grunt before running the Grunt command line. Leave this cleared if you are installing Grunt with a separate preceding NPM action. [–npm]
Run NPM Using
The Using drop down is populated by any property collector properties whose namespace matches the pattern defined by the NPM action. The pattern for this action is ^NPM.*
If you create a property collector for this pre-install action, make sure you select the Path Finder PlugIn type and give it a name that will match the pattern above in blue. Example names listed here, search the table's Plugin column for "NPM".
For more in-depth explanations on property collectors see Property Collectors.
Alternatively, you can select the Custom option from the Using drop down list and specify a path in the resulting input field that will be displayed. Please read Why it's a good idea to use a property collector before using this option.
Options
Force your way past warnings
Tick this to use the --force argument to ignore warnings. [---force]
Log standard output
Tick this to log output from the Grunt command line.
Verbose logging
Tick this to pass the --verbose argument to get more detailed output from the Grunt command line. [---verbose]
Debug logging
Tick this to pass the --debug argument to get more diagnostic output from the Grunt command line. [---debug]
Timeout (in seconds)
How long to wait for the action to finish running before timing out. Leaving this blank (or zero) will default to 86400 seconds (24 hours).
Treat failure as warning
Tick to continue build on failure marking the action with a warning status.
Ignore warnings
If this is ticked, any warnings logged will not mark the action with a warning status.
Environment
Environment Variables
Multiple environment variables can be defined - one per line. These are set before the command line is run.
Log environment variables
If this is ticked, environment variable values are written to the build log.
Generate system environment variables
Tick this checkbox to set up a list of new environment variables prefixed with 'ContinuaCI.' for all current system expression objects and variables.
Mask sensitive variable values in system environment variables
This checkbox is visible only if the 'Generate system environment variables' checkbox is ticked.
If this is ticked, the values of any variables marked as sensitive will be masked with **** when setting system environment variables. Clear this to expose the values.