The Atlassian CLI family consists of both server (connector) and client components. This describes the various add-ons and their relationship. See Atlassian CLI License for licensing related information.
- Some Atlassian CLI clients require a connector app be installed on the Atlassian application that is intended to be accessed. Connector app installation must be done by a system administrator.
- The Atlassian CLI is not just a powerful client based interface, but is also available as an embedded service in Run CLI apps and other apps! Run CLI app installation must be done by a system administrator.
- Provides a connection between clients included in the Atlassian CLI app and their corresponding Atlassian application instance.
- A system administrator must install and license a connector in order for a client to run actions for the application instance.
- All-in-one embedded solution.
All the power of every CLI client —embedded in your Atlassian app.
- Execute CLI actions right within your Atlassian apps:
- via workflow functions or UI in Jira
- via macros in Confluence
- Integrate and automate any CLI supported external app.
- Bamboo is not available for Cloud.
- Bitbucket connector is not available for Cloud as the Bitbucket Cloud client does not need a connector.
Server add-ons are UPM installed add-ons that provide server specific capabilities. There are two types of server add-ons.
Clients are standalone command line tools installed on any system (Windows, Linux, OSX) with Java 1.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.
See CLI Client Installation and Use.