The Bower update action is used to update installed Bower packages to their newest version according to the specifications in the bower.json file.
Bower Update
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.
Package Directory
Where the packages to update are located. Relative paths will be anchored to the workspace folder.
Package Name(s)
A list of package names separated by spaces.
Using
The property collector pointing to the location of the Bower.cmd file.
Options
Production mode
Tick to apply the --production argument if you do not wish to update devDependencies.
Force latest
Tick to apply the --force-latest argument which will force an update to the latest version if there is a conflict.
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.
Log standard output
Tick to log the Bower output to the build log.
Verbose logging
Tick to log a more verbose Bower output
Environment
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
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.