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.
We are getting an error in versining when we are trying to a build job in gitlab. Both in 2.5.9 and 2.5.11. The errors always revolves around "org.eclipse.jgit.api.errors.JGitInternalException: Could not rename file". THis mostly happens when multiple branch are there. Anyone has experienced same issue and how they resolved it ?
Can you please provide more information? For example, which command did you run when you saw the error? Which OS?
Yes we were creating a new branch from the master. We had used -branch_name.
Were you checking out the branch outside of the tool? It should be able to switch branches if you use the "-branch_name" option.
I guess we have found what was wrong.
When a new branch is created from master the versioning configuration was getting copied which was referring to master branch. After changing the configuration in the new branch to refer the new branch, we have not seen this issue occurring.
We have not tried with GitHub. It work in local machine. If we can get some details on when and why the rename operation happens maybe we can troubleshoot.