This utility is planned to be archived later this year. The features provided by it are available out of the box (OOTB) in Appian versions 23.2+. For more information, refer to the Deployment APIs documentation.
Overview
This utility automates the process of inspecting the application, executing DDL scripts, updating CDTs, republishing the appropriate datastores, and importing the application.
With the Automated Import Manager Client, users can automatically deploy applications and package contents (either applications from Appian OR packages generated from the Automated Versioning Manager) to any environment. This utility provides the scripts that support triggering deployments from an external CI tool or deploy from the command line.
Key Features & Functionality
Automated Import Manager:
For more information, please see visit: https://community.appian.com/w/the-appian-playbook/198/deployment-automation
Note: This utility does not support Java version 9.0.
In the deployments tab/deployments detail you will be able to see the name of the applications imported.
After importing application, in admin console history not showing name of the application. it is showing as "ImportExportService Import 2021-11-03 19:28:44.803"
Thanks, pmagalhaes. I'd like to add that the same applies to GitHub.
It works if you use a token as the password, at least with Bitbucket.
What happens if developer 1 checks in a version of object A, and then developer 2 checks in an *earlier* version of A? It can happen if both are working on the same object, and 2 creates a package before 1, but 1 checks in package to Git before 2. It the tool smart enough to know its trying to overwrite a later version with an earlier one?
In our case we are trying to build only one application . So we are using "buildsingleapp".