Automated Versioning Manager (AVM)

RE: Automated Versioning Manager (AVM)

JanTichava — Mon, 22 Sep 2025 09:25:46 GMT

I know that my question is more related to "export" of the application, but why Decision object has a new "versionKey" everytime? That causes difference in a commit. Thank you. (applicationHaul tag value of Application also, but that's understandable)

RE: Automated Versioning Manager (AVM)

karthigeyanr860306 — Wed, 06 Aug 2025 02:14:03 GMT

When i download the plug in , I'm getting an empty zip file

RE: Automated Versioning Manager (AVM)

Appian AppMarket — Fri, 09 May 2025 10:00:00 GMT

v2.6.2 Release Notes

Upgraded the plugin to make it compatible with Appian version 25.1 and above. Also added the old version of the utility as a supplemental file for users below 25.1 version.

RE: Automated Versioning Manager (AVM)

rajj — Wed, 23 Apr 2025 12:13:19 GMT

Hi,

When trying to install this for Appian on Appian Government Cloud (version 24.3.900.0) using the "Use this utility for Appian Versions below 25.1.zip" in the extracted zip, we encounter this error message.

2025-04-22 19:28:05,740 [Appian Plugin Hot Deploy] ERROR com.atlassian.plugin.loaders.ScanningPluginLoader - Unable to deploy plugin 'null' from 'Unit: /usr/local/appian/_admin/plugins/Automated Versioning Manager (AVM) 2.5.33.zip (1745349997000)'. 2025-04-22 19:28:05,740 [Appian Plugin Hot Deploy] ERROR com.atlassian.plugin.loaders.ScanningPluginLoader - Because of the following exception: com.appiancorp.plugins.component.ComponentPluginParseException: COMPONENT_PLUGIN_ERROR_TOKENCould not parse zip file - make sure it is formatted properly at com.appiancorp.plugins.component.ComponentPluginXmlResolver.isDeprecatedDefinitionXml(ComponentPluginXmlResolver.java:53) at com.appiancorp.plugins.component.ComponentPluginXmlResolver.getPluginXml(ComponentPluginXmlResolver.java:33) at com.appiancorp.plugins.component.ComponentPluginFactory.canCreate(ComponentPluginFactory.java:85) at com.appiancorp.plugins.osgi.LoggingPluginFactoryDecorator.canCreate(LoggingPluginFactoryDecorator.java:28) at com.atlassian.plugin.loaders.ScanningPluginLoader.deployPluginFromUnit(ScanningPluginLoader.java:142) at com.atlassian.plugin.loaders.ScanningPluginLoader.loadFoundPlugins(ScanningPluginLoader.java:113) at com.appiancorp.plugins.loaders.UnloadingDirectoryPluginLoader.loadFoundPlugins(UnloadingDirectoryPluginLoader.java:55) at com.appiancorp.plugins.loaders.PluginVersion2DefaultLoader.loadFoundPlugins(PluginVersion2DefaultLoader.java:47) at com.atlassian.plugin.loaders.PermissionCheckingPluginLoader.loadFoundPlugins(PermissionCheckingPluginLoader.java:31) at com.atlassian.plugin.manager.DefaultPluginManager.lambda$scanForNewPlugins$14(DefaultPluginManager.java:881) at com.atlassian.plugin.manager.PluginTransactionContext.wrap(PluginTransactionContext.java:63) at com.atlassian.plugin.manager.DefaultPluginManager.scanForNewPlugins(DefaultPluginManager.java:877) at com.appiancorp.plugins.AppianPluginManager.scanForNewPlugins0(AppianPluginManager.java:193) at com.appiancorp.plugins.AppianPluginManager.scanForNewPlugins(AppianPluginManager.java:185) at com.appiancorp.plugins.HotDeployerRunnable.run(HotDeployerRunnable.java:28) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) at java.base/java.lang.Thread.run(Thread.java:840) 2025-04-22 19:28:05,741 [Appian Plugin Hot Deploy] ERROR com.appiancorp.plugins.LoggingPluginEventListener - Failed to load Component Plug-in 'Automated Versioning Manager (AVM) 2.5.33.zip': Could not parse zip file - make sure it is formatted properly

RE: Automated Versioning Manager (AVM)

rajj — Wed, 23 Apr 2025 12:08:46 GMT

Hi,

When trying to deploy the "Utility for Appian Versions below 25.1", we get this error message. Please advise.

RE: Automated Versioning Manager (AVM)

Appian AppMarket — Mon, 14 Apr 2025 22:00:00 GMT

v2.6.0 Release Notes

Replaced metaparadigm json rpc with appian json rpc to make the plugin compatible with Appian 25.1+ versions.

RE: Automated Versioning Manager (AVM)

griffinp600565 — Tue, 25 Feb 2025 16:35:14 GMT

Hi all,

We're attempting to install this plugin on a self hosted Appian on Kubernetes solution. We're on version 24.2.585. With all other plugins we just drop the plugin jar in the {APPIAN_HOME}/ae/_admin/plugins and they start up with no error.

With this plugin we're getting

Failed to enable Plug-in 'appian-adm-versioning-client-2.5.33.jar' (appian-adm-versioning-client-2.5.33.jar) version 0.0: 'No plugin factories found for plugin file Unit: {APPIAN_HOME}/ae/_admin/plugins/appian-adm-versioning-client-2.5.33.jar (1740434030985). Does it contain an appian-plugin.xml file?'

We've done some research and it seems like this is something that should be included in the jar. Is there anything we're missing or did we grab a wrong version of the plugin that doesn't work with our current appian version?

RE: Automated Versioning Manager (AVM)

Appian AppMarket — Wed, 15 Jan 2025 11:00:00 GMT

v2.5.33 Release Notes

Upgraded Commons-IO Library for security fix

RE: Automated Versioning Manager (AVM)

Appian AppMarket — Thu, 10 Oct 2024 22:00:00 GMT

v2.5.32 Release Notes

Upgraded the org eclipse jgit version

RE: Automated Versioning Manager (AVM)

josep — Fri, 06 Sep 2024 14:37:50 GMT

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 ?

RE: Automated Versioning Manager (AVM)

Shubham Gupta — Mon, 08 Apr 2024 22:55:40 GMT

Hi Team ,

I am facing the below error When I am taking addContent Action.

It is saying Git Authentication failed while pushing the changes to Git, I am not able to understand if there is an authentication issue then how it cloned the remote repo to the local repo. JUST FYI there is no two-way authentication in my remote repository.

Please if any one has any idea then help me.

thanks

RE: Automated Versioning Manager (AVM)

Shubham Gupta — Mon, 08 Apr 2024 12:32:33 GMT

Hi Team ,

I am new to DevOps , I am facing the below two errors , Please have a look

1 ) When I am taking action updateRepo , Cloning Done successfully but at the end it seems some error, please find the highlighted context in red in the attached document.

RE: Automated Versioning Manager (AVM)

Appian AppMarket — Tue, 01 Aug 2023 22:01:28 GMT

v2.5.30 Release Notes

Changed the settings so logging is now on by default

RE: Automated Versioning Manager (AVM)

tanveers0002 — Tue, 30 May 2023 13:35:36 GMT

i am not able to download this utility , getting network error

RE: Automated Versioning Manager (AVM)

Appian AppMarket — Thu, 23 Mar 2023 21:58:59 GMT

v2.5.26 Release Notes

Updates to Zip4j library