Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Version published after converting to the new editor

Info
With the release of the WhiteSource Unified Agent (previously called the File System Agent (FSA)), WhiteSource will no longer provide standard support, including updates and fixes for the NPM plugin after May 4th, 2019. 
Extended Support (limited to configuration & support/troubleshooting) will be provided until November 1st, 2019. Please migrate to the Unified Agent before this date. This plugin will no longer be supported by WhiteSource on November 2nd, 2019.
The WhiteSource Support team is ready to assist with the necessary changes required to use the Unified Agent and can be contacted via the Customer Community.   

...

AttributeTypeDescriptionRequired
apiKeyStringUnique identifier of the organization to update, can be retrieved from the admin page in your WhiteSource account.Yes
checkPoliciesBooleanWhether or not to send the check policies request before updating WhiteSource.No
productNameStringName of the product to update.No, if not defined matching to existing WhiteSource products is done by productToken
productVerStringVersion of the product and project to update. This overrides the project version.No, only read if productName is defined
productTokenStringAPI token to match an existing WhiteSource product, can be retrieved from the Integration API page in your WhiteSource account.No, if not defined matching to existing WhiteSource products is done by name. No projectToken is allowed
projectNameStringName of the project to update.No, if not defined matching to existing WhiteSource projects is done by projectToken
projectVerStringVersion of the project.No, only read if projectName is defined
projectTokenStringAPI token to match an existing WhiteSource project, can be retrieved from the Integration API page in your WhiteSource account.No, if not defined matching to existing WhiteSource projects is done by name. No productToken is allowed
devDepStringAdds devDependencies to the WhiteSource report. Accepts either "true" or "false"No
baseURLStringThe IP / Name of the destination WhiteSource serviceNo. Will use the default configuration
portIntThe port number of the destination baseURLNo. Will use the default configuration
httpsBooleanWhether or not to use HTTPS secured connectionNo. Will use the default configuration
proxyStringThe proxy server from which you want to redirect the messages. (e.g - "proxy":"http://10.0.0.1:8080" )No
forceUpdateBooleanIf true - updates the project even if the "checkPolicies" step failed. (default is false)No. Will use the default configuration
failOnErrorBooleanIf true, fails the process if "checkPolicies" failed (default is false)No. Will use the default configuration
timeoutMinutesIntNumber of minutes to timeout. (default is one hour) No. Will use the default configuration
debugModeBooleanIf true, adds to the root folder a new folder with log files. (default is false)No. Will use the default configuration
registryAccessTokenStringAccess token to private registriesNo
connectionRetriesintConnection retries when unable to connect to WhiteSource service. (default is 1)No. Will use the default configuration
failOnConnectionErrorBooleanFails the build when unable to connect to WhiteSource serviceNo, default value is true
userKeyStringUnique identifier of the user who updates, can be retrieved from the admin page in your WhiteSource account.Required if WhiteSource administrator has enabled "Enforce user level access" option
ignoreNpmLsErrorsBooleanWhether or not to ignore errors of the 'npm ls' command.No, the default value is false

Resolving NPM Dependencies

...

If you scan a private registry that requires an access token, add the property "registryAccessToken" to the WhiteSource config file.

Info

Supported from version 17.12.4

Executing the Plugin

Make sure you have package.json and whitesource.config.json files located at project root.

...

The exit codes WhiteSource returns in the Bash command language should be treated as 'x' modulo 256: 

  • Exit code 0 is equivalent to code 0 (0 mod 256 = 0)
  • Exit code -1 is equivalent to code 255 (-1 mod 256 = 255)
  • Exit code -2 is equivalent to code 254 (-2 mod 256 = 254)
  • Exit code -3 is equivalent to code 253 (-3 mod 256 = 253)
  • Exit code -4 is equivalent to code 252 (-4 mod 256 = 252)
  • Exit code -5 is equivalent to code 251 (-5 mod 256 = 251)

...