...
Summary
The Atlassian CLI family (since version 4.x) consists of both server and client elements (connector) and client components. This describes the various add-ons and their relationship. See Atlassian CLI License for licensing related information.
...
| Include Page |
|---|
| _CLIToolFamily |
|---|
| _CLIToolFamily |
|---|
|
...
...
...
...
...
- Bamboo Cloud is supported
- A connect add-on is not needed or available currently
Server
Server add-ons are UPM installed add-ons that provide server specific capabilities. There are two types of server add-ons.
| Table plus |
|---|
| Type | Description |
|---|
| CLI Connector | This is a component of the CLI add-ons that installs on the Atlassian server and provides REST API services for CLI clients or Run CLI Action connections. | | Run CLI Actions | These are product-specific add-ons that bundle Atlassian CLI capabilities within product specific functionality - Atlassian CLI actions are specified in the same syntax and run virtually the same code from within the product as would be case if run from a command line.
| Table plus |
|---|
| Server | Description |
|---|
| JIRA | - Workflow post functions and validators that run CLI actions
- Menu interface for administrators to run CLI actions
| | Confluence | - Macro to run CLI actions based on user input or show content constructed from CLI actions
| | Bamboo | - Tasks to run CLI actions in build and deployment plans
| | Bitbucket |
|
|
|
...
| - Commit hook to run CLI actions
|
|
|
|
Clients
Clients are standalone command line tools installed on any system (Windows, Linux, OSX) with Java 1.7 8 or higher. Clients access Atlassian products via remote APIs. Clients are installed by downloading and unpacking the distribution zip. Clients are included with any server add-on purchase and may require an installed server add-on for each server they connect with.
...
