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.
I use ssh key to get access to my GitLab repository and not a username and password. When I use the versioning-client I get an Auth fail when try to push contents to my repository.
Details of error: org.eclipse.jgit.api.errors.TransportException: git@gitlab.my-git-details.git: Auth fail
I have gotten this to work on Linux, but not Windows. Most of our users are on Windows so this is an issue. Has anybody else experienced this?
I have gotten around the auth error by using Putty instead of OpenSSH. Unfortunately I have a new problem. The version-application runs, but does not do anything and does not respond when I try kill it.
Hello brendonp, for GitLab you can create an access token to use in the password field in the properties file as opposed to your actual password. To do so, you can follow this link here: https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html. For the repoUrl, make sure to use the https URL instead of ssh. This way, it will function the same as if you used ssh without jeopardizing your password. Please let us know if you have any additional questions.