The features provided by this utility are now 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.
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".
Have you tried using "buildAllApps"?
Hi, suvasisb. Right now, it only supports Git repositories.
While trying the buildSingleApp action does it consider packaging the DDL file in the package?
I am unable to deploy the application using the deployment Automation manager (import manager ) , as the package generated by AVM is not containing the ddl files to execute, but the metadata property file refers to ddl file and the deployment fails because of the same.
Hi, aravinds0003. When you are importing a deployment automation package (this is different from an application or patch ZIP), you should not be be adding DDLs separately since they should already be specified in the package itself. I hope this helps.
we are facing below issue : "Status: Failed. Current step: . Error message: Error in the configuration of the deployment. Data source and DDL cannot be provided when supplying an automated deployment package.."
We are using sql server . Not sure what we are missing here?
Is it compatible with https://azure.microsoft.com/en-us/services/devops/repos/ ?
This means it couldn't find test.sql. Can you please double-check to make sure it's at the location specified in the properties file?