Table of Contents
...
Selecting a Plugin for Integration
| Info |
|---|
WhiteSource recommends using the Unified Agent. |
| Language | Plugin |
|---|---|
| Java | Unified Agent, Maven, Jenkins, TeamCity |
| .Net | Unified Agent, TFS/VSTS, Jenkins, TeamCity |
| Scala | Unified Agent, Maven , Jenkins, TeamCity |
| Clojure | Unified Agent, Maven , Jenkins, TeamCity |
| C# | Unified Agent, TFS/VSTS, Jenkins, TeamCity |
| Ruby | Unified Agent |
| Python | Unified Agent |
| NPM | Unified Agent, NPM |
| NuGet | Unified Agent |
| Bower | Unified Agent, NPM |
| C/C++ | Unified Agent |
| Obj-C | Unified Agent |
| JavaScript | Unified Agent, Jenkins |
| PHP | Unified Agent |
| Go | Unified Agent |
| RPM/YUM | Unified Agent |
| Debian | Unified Agent |
| Swift | Unified Agent |
| Alpine Linux | Unified Agent |
| Groovy | Unified Agent |
| ActionScript | Unified Agent |
| Arch Linux | Unified Agent |
...
Overview and Default Behavior
If a scanned project uses a configuration file that contains only a defined 'projectName' (where 'projectToken’, ‘productName’ and ‘productToken’ are left empty), then the Unified Agent adds the results to the first project it finds in the organization that contains the same project name.
If a multi-module project is scanned with the same configuration as described above, and a project with one of the module names already exists, then the Unified Agent adds the module data to this existing project.
| Code Block | ||
|---|---|---|
| ||
projectName=NewProject projectToken= productName= productToken= |
Changing the Default Behavior
In order to avoid overriding an existing project with the same name, from the Advanced Settings section of the Integrate page, select the checkbox Add project to default product when only project name is provided.
When this checkbox is selected, the following rules apply to all future scans:
...