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

Compare with Current View Page History

« Previous Version 4 Next »

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.

The Bower Install action is used to install Bower packages to the workspace.

Bower Install

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 namejquery
normalize.css
Git endpointhttps://github.com/user/package.git
git@github.com:user/package.git
Git endpoint without .gitgit+https://github.com/user/package
git+ssh://git@github.com/user/package
Local foldermy/local/folder/
Public Subversion endpointsvn+http://package.googlecode.com/svn/
Private Subversion endpointsvn+ssh://package.googlecode.com/svn/
svn+https://package.googlecode.com/svn/
Shorthand (defaults to GitHub)user/package
URLhttp://example.com/script.js
http://example.com/style.css
http://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>


Using

The property collector pointing to the location of the Bower.cmd file.


Options


Several options are provided for specifying how and where the packages should be saved. Each option is described on the Options tab.

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 Bower command line is run.


  • No labels