Appian Community and Appian Academy are being upgraded. From July 24–August 3, the Appian Community will be in read-only mode. During this time, the site will be read-only and user registration will be disabled. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
ContextFor a client I'm currently making use of the Automated Deployment Manager plugin, in this case specifically the deploy-application.sh script. Everything is working fine right now, however we have a specific requirement ask that I'm having difficulty with:
Currently, a Deployment through this plugin will halt if the Inspection yields any Error messages it seems. My client wants to be able to have deployments halted upon Warnings coming back as well. I can think of a workaround by doing an Inspect, digging through the result log for Warnings, and using a Process Model / Parent-Script logic flow to halt then conditionally do the Inspect/Deploy action, but that seems inefficient as it forces 2 separate Inspect actions upon a successful deployment.
Question
Is there any way to instruct the ADM script to halt on Inspect Warnings as well as Inspect Errors, and if not does Appian have any recommendations on what modifications could be made within the scripts to accomplish this?
Discussion posts and replies are publicly visible