Versions Compared

Old Version 10

changes.mady.by.user Bob Swift

Saved on

compared with

New Version 11

changes.mady.by.user Bob Swift

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

We always are sensitive to upward compatibility of our offerings and specifically want to make sure CLI scripts are as upward compatible as possible at least with the respect to those aspects that are under our control. Most of our actions remain compatible across a wide range of application releases and even to high degree across different environments (Cloud and Data Center). However, on a CLI version boundary, we do take the opportunity to remove previously deprecated support or make some changes especially where it will simplify new user experiences and remove clutter for users.

This page describes some of the important changes to be aware of when upgrading to 12.x from 11.x or earlier. If upgrading from release prior to 11.x, see also Special Compatibility Notice for ACLI Version 11.x.

Client Changes

Client

Change

Replacement

Discussion

bamboo

removed

bitbucketcloud

Continue to use ACLI release 11.3

The bamboo client was deprecated in ACLI release 11.2 and now is being removed from the distribution.

This was a difficult decision for us. We started supporting Bamboo in 2007 and it one of our largest clients with over 200 actions. Internally, we have used Bamboo extensively over the years. In late 2021, we started our migration to Bitbucket Pipelines. ACLI products completed migration a few months later and other Appfire apps followed. Bamboo 9.x is still in use by some Appfire products.

With the Feb 2024 discontinuance notice for Bamboo Server by Atlassian, we supported customer migration to Bamboo Data Center in ACLI release 11.0 so that Bamboo customers will still be supported by ACLI with ACLI release 11.3 for some time running against Bamboo Data Center 9.2 (LTS) - 9.5. However, Bamboo 9.5 will be the last officially supported release as we have discontinued testing for Bamboo releases and removing the bamboo client starting with ACLI release 12.0.

Over the last years, we have invested significantly in the Bitbucket Cloud client and especially the pipeline support to enable customers using Bitbucket Cloud and especially those customer with Bamboo migration efforts.     

jsm

removed

Continue to use ACLI release 11.3

The jsm client was deprecated in ACLI release 11.2 and now is being removed from the distribution. 

Jira Service Management customers can continue to use the Jira client for accessing Jira information in JSM instances just like before, but we are no longer supporting JSM specific actions. 

tempo

removed

Continue to use ACLI release 11.3

The tempo client was deprecated in ACLI release 11.1 and now is being removed from the distribution.

We were unable to provide meaningful and credible coverage of Tempo capabilities, so we have decided to discontinue the limited support we had. Our existing support in the Jira client for some Tempo custom fields will continue as normal. 

trello

removed

Continue to use ACLI release 11.3

The trello client was deprecated in ACLI release 11.1 and now is being removed from the distribution.

Low customer interest. We were unable to continue to extend our coverage of Trello capabilities, so we have decided to discontinue the support. 

segment

removed

Continue to use ACLI release 11.3

The segment client was deprecated in ACLI release 11.1 and now is being removed from the distribution.

Low customer interest. 

keen

removed

Continue to use ACLI release 11.3

The keen client was deprecated in ACLI release 11.1 and now is being removed from the distribution.

Low customer interest.

...

Clients

Action

Change

Reason

bitbucketcloud

getCommitList, runFromCommitList

getDeploymentList, runFromDeploymentList

getPipelineList, runFromPipelineList,

getCommit (only when using --commit @last and other filtering parameters)

getPipeline (only when using --pipeline @last and other filtering parameters)

Defaults to most recent items. Equivalent to setting the startDate parameter to -30d or @default.

Improve performance:
Commits, deployments, and pipelines are continuously being added and can easily grow to a large number of items. Unless a limit parameter is provided, the entire list might have to be evaluated to produce the desired list. Limiting by default prevents accidental long running requests. Use --startDate @all to avoid the default or specify a specific startDate based on your needs.

bitbucketcloud

getBranchList, getBranch (name search)

getPullRequest, getPullRequest (name search)

Defaults to most recent items. Equivalent to setting the startDate parameter to -365d or @default.

Similar to above.

bitbucketclou

getPullRequestList column order

The author columns were moved after the merge commit column

Having the author fields before the pull request field did not follow standards. Script writers are now encouraged with 12.0 to explicitly list the columns they need in the order they want in the columns parameter to best protect the script from future changes.

Removed Actions

Clients

Removed

Replacement

Discussion

cli

provideFeedback


This was done through a Keen service no longer available

...