Deployment Automation Manager

The Deployment Automation Manager consists of two tools used for:

  • Automating application deployments in Appian (Automated Import Manager)
  • Change management for Appian applications (Automated Versioning Manager)

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:

  • 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.

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

Anonymous
Parents
  • A couple questions.

    1. What changes were made in the July update?

    2. Is there an issue with the automation manager pushing code to GIT?

    I use PortableGit to push Appian Applications to BitBucket. Last month I noticed that the automation manager unzips my application into the appropriate files locally and sends a commit message to Bitbucket but it no longer pushes the files. I thought it was because I was still on client version 2.5.7 but its still happening with version 2.5.8. My current work around is to manually add all changes and push it to my branch using git. Does anyone else experience this? How can I troubleshoot this as none of my configurations in version-manager.properties have changed?

Comment
  • A couple questions.

    1. What changes were made in the July update?

    2. Is there an issue with the automation manager pushing code to GIT?

    I use PortableGit to push Appian Applications to BitBucket. Last month I noticed that the automation manager unzips my application into the appropriate files locally and sends a commit message to Bitbucket but it no longer pushes the files. I thought it was because I was still on client version 2.5.7 but its still happening with version 2.5.8. My current work around is to manually add all changes and push it to my branch using git. Does anyone else experience this? How can I troubleshoot this as none of my configurations in version-manager.properties have changed?

Children