| 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 |
|---|
|
| | |
Image Removed
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 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 |
|---|
| CLI Connector | 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
| | Stash | - Commit hook to run CLI actions
|
|
|
|
Clients
Clients are standalone command line tools installed on any system (Windows, Linux, OSX) with Java and accesses 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 |
|---|
|
