The Deployment Automation Manager consists of two tools used for:
Although the tools are best used in conjunction, they can be used independently as well.
The Automated Versioning Manager is a tool that helps manage Appian applications and database DDL files in a version control system. Given an Appian application ZIP file, the Automated Versioning Manager performs the following actions:
The goal of this tool is to facilitate the adoption and usage of a version control system to perform configuration management of the Appian applications and database DDL files.
With the Automated Import Manager, users can automatically deploy applications and patch contents (either applications from Appian OR packages generated from the Automated Versioning Manager) to any environment. Users will have three options for deployment: the tool can either deploy from the tool’s user interface in one click, trigger the deployment from an external CI tool or deploy from the command line.
The Automated Import Manager automates the process of inspecting the application, executing DDL scripts, updating CDTs, republishing the appropriate datastores, and importing the application.
For more information, please visit: https://community.appian.com/w/the-appian-playbook/198/deployment-automation
while testing this with svn I faced an issue like this "org.tmatesoft.svn.core.SVNAuthenticationException: svn: E170001: Negotiate authentication failed: 'No valid credentials provided'
the solution was to override the order of the authentication methods by adding the following on the version-appliation.bat "DEFAULT_JVM_OPTS=-Dsvnkit.http.methods=Basic" in case the svn has Basic authentication. Or we can use any of the other options like this "DEFAULT_JVM_OPTS=-Dsvnkit.http.methods=Basic,Digest,Negotiate,NTLM" it will depend on your needs
© 2020 Appian. All rights reserved.