| Include Page |
|---|
| info:css-home |
|---|
| info:css-home |
|---|
|
| Div |
|---|
|
On this page| Table of Contents |
|---|
| maxLevel | 2 |
|---|
| minLevel | 1 |
|---|
| exclude | On this page |
|---|
| type | flat |
|---|
| separator |
|---|
|
| | |
Summary
The Atlassian CLI family for Version 4 consists of both server and client elements. This describes the various add-ons and their relationship. See Atlassian CLI license for Versions 4.x for licensing related information.
CLI Add-ons
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 |
|---|
| REST Services | Provides REST API services for CLI clients or for direct access. | | Run CLI Actions | These are product-specific add-ons that bundle ACLI capabilities within product specific functionality - ACLI 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 ACLI actions
- Menu interface for administrators to run ACLI actions
| | Confluence | - Macro to run ACLI actions based on user input or show content constructed from ACLI actions
| | Bamboo | - Tasks to run ACLI actions in build and deployment plans
| | Stash | - Commit hook to run ACLI actions
|
|
|
|
Clients
Clients are standalone command line tools installed on a local system (PC or server) and 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 require an installed server add-on for each server they connect with.
See Client Downloads.
...
| Include Page |
|---|
| Understanding the Appfire CLI |
|---|
| Understanding the Appfire CLI |
|---|
|
