The Bower Actions in Continua are a wrapper around the Bower command line. If you're having trouble using any of the Bower actions, please refer to the Bower Command Line Reference.
Bower Install Action
The Bower Install action is used to install Bower packages to the workspace
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.
Target Directory
Where to install the package. Relative paths will be anchored to the workspace folder.
Endpoints
A list of package endpoints specified one per line.
Endpoints can have multiple forms:
<package><package>#<version><name>=<package>#<version>
Where:
<package>is a package URL, physical location or registry name<version>is a valid range, commit, branch, etc.<name>is the name it should have locally.
<package> can be any one of the following:
| Registered package name | jquerynormalize.css |
| Git endpoint | https://github.com/user/package.gitgit@github.com:user/package.git |
| Git endpoint without .git | git+https://github.com/user/packagegit+ssh://git@github.com/user/package |
| Local folder | my/local/folder/ |
| Public Subversion endpoint | svn+http://package.googlecode.com/svn/ |
| Private Subversion endpoint | svn+ssh://package.googlecode.com/svn/svn+https://package.googlecode.com/svn/ |
| Shorthand (defaults to GitHub) | user/package |
| URL | http://example.com/script.jshttp://example.com/style.csshttp://example.com/package.zip (contents will be extracted)http://example.com/package.tar (contents will be extracted) |
A version can be:
| semver version | #1.2.3 |
| version range | #1.2#~1.2.3#^1.2.3#>=1.2.3 <2.0 |
| Git tag | #<tag> |
| Git commit SHA | #<sha> |
| Git branch | #<branch> |
| Subversion revision | #<revision> |
Log standard output
Tick to log the Bower output to the build log.
Verbose logging
Tick to log a more verbose Bower output
Using
The property collector pointing to the location of the Bower.cmd file.
