Overview
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:
This tool is frequently used with the native, external deployment APIs (https://docs.appian.com/suite/help/22.1/Deployment_Rest_API.html) or the Automated Import Manager (AIM) (https://community.appian.com/w/the-appian-playbook/198/deployment-automation). Unless you are doing deployments for the Admin Console, we suggest using the native APIs.
Key Features & Functionality
You can access the source code for AVM by exploding the ZIP file after download.
Note: This utility does not support Java version 9.0.
Hello,
We have one requirement from client where they want to use Appian as Git project. They want the ability of editing one object by more than one developer and use branching, merging to merge the code. They want to set up complete CI/CD. Will this AVM will be useful for that?
Technically, that is what this tool is for, however, the versioning manager explodes the application zip file that contains the source. The source is not standard SAIL code, it is an XML format that wraps the SAIL code. This is not very useful for merging code changes. Really, this tool is only useful to keep an auditable record of code.
Our team develops in the cloud, using the tools provided in Designer to manage code changes and versions, restricting a single developer to each object. This is not ideal, but it works fairly well. It would be really great to have the concept of code branches and merging, but SAIL and Designer is not set up for this yet.