Automated Versioning Manager (AVM)

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:

  • Unzips the application and organizes the artifact XML files in the repository.
  • Automates the check-in and check-out operations with the version control system.
  • Generates application packages for import in Appian based on the contents of the repository and a range of changes to include.

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

  • Version Control integration (Git, SVN)
  • Supports Appian applications and packages
  • Generate import package from hash ranges
  • Folder Listener to add contents to Version Control
  • Supports GitHub, GitLab, and BitBucket for Version Control

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. 

Anonymous
Parents
  • we just found an issue that the process models got supper indented for example one expression ont he export came <expr>CODE</expr> it became 3 lines

    <expr>

        CODE

    </expr>

    This is causing the process models render to see really awful, and hard to read and understand. 

    I looked at the commits and the only commit that introduced the spaces came from the AVM addContents tool before that commit the repor code was great and the patch was ko too. 

    I found on the code that every time we run the tool to add content the AVM tool is opening the xml , loading as XML document in Java, then it adds a comment at the end and write the document using the following lines 

    ------------------

    xformer.setOutputProperty(OutputKeys.INDENT, "yes");
    xformer.setOutputProperty("{">xml.apache.org/xslt}indent-amount", "4");

    ------------------

    So far this is my only suspect in the process that caused this situation. 

    have anybody experienced similar situation ?

Comment
  • we just found an issue that the process models got supper indented for example one expression ont he export came <expr>CODE</expr> it became 3 lines

    <expr>

        CODE

    </expr>

    This is causing the process models render to see really awful, and hard to read and understand. 

    I looked at the commits and the only commit that introduced the spaces came from the AVM addContents tool before that commit the repor code was great and the patch was ko too. 

    I found on the code that every time we run the tool to add content the AVM tool is opening the xml , loading as XML document in Java, then it adds a comment at the end and write the document using the following lines 

    ------------------

    xformer.setOutputProperty(OutputKeys.INDENT, "yes");
    xformer.setOutputProperty("{">xml.apache.org/xslt}indent-amount", "4");

    ------------------

    So far this is my only suspect in the process that caused this situation. 

    have anybody experienced similar situation ?

Children
No Data