26 Feb 2012
This release focused on expanding JIRA support, cross product improvements, and covering new product releases, especially JIRA 5.0. This is a simultaneous release of all CLI clients except for the Crowd CLI - see note. The Atlassian CLI distribution contains all CLI clients (except Crowd) plus the atlassian script and additional examples and help text shipped with the distribution.
The Atlassian Command Line Interface (CLI) supports a large range of product releases. The matrix below provides compatibility guidelines based on testing, API compatibility information provided in Atlassian, and community feedback. User's are encourage to help improve compatibility information through discussions and issues. The CLI also works with releases not officially listed here since in many cases it uses remote APIs provided by Atlassian that have been stable for many years. Check previous versions of the CLI for coverage of earlier releases. Users should verify their usage scenarios on new releases. Support normally is limited to minimum releases indicated. Client requires Java 1.6 (recommended) or above. Testing is only done on Java 1.6. In some cases, new actions are only available on against later versions of the server - these are usually noted in the documentation.
3.1 - 3.5 and 4.0 - 4.1 (Note 1)
|3.4.0, 3.5.13, 4.1.0|
4.0 - 4.4 (Note 2 and 3) and 5.0
|4.3.3, 4.4.4, 5.0.0|
3.2 - 3.4 (Note 4 and 5)
2.2 - 2.7
2.2 - 2.7
More details are available on the add-on page - Run CLI Actions in Confluence
2.4.0 was the first release of this add-on. It is planned to concurrently release this add-on with each new release of the Atlassian CLI.
Crowd CLI removed from distribution
Crowd Command Line Interface (CLI) has been temporarily suspended from further development until the APIs are improved. As previously noted, Atlassian completely removed the Crowd remote APIs used for the CLI starting with Crowd 2.1. New replacement APIs do not cover most of the existing functionality. Atlassian is currently targeting application use cases and not automation capabilities for the Crowd APIs. It will be a while to sort out how the Crowd CLI moves forward, until then, the Crowd CLI has been removed from the distribution.