|
|
I am not stowing on the mainframe anymore (upload and stow=no in deploy.xml) until I can be 100% certain the problem will not occur again (hence why I have asked for an incremental failsafe property to be added in the next release / update below).
Proposed property / “incremental deploy failsafe property”: e.g. -pMaxModules=x
I proposed adding a new property to the ant execution to backout and throw an exception as I thought a limiting parameter would be useful for ‘incremental’ deploys in a “worst case scenario” if it identifies more changes than intended / tries to stow more than a set property limit.
Every time this problem occurs, I have to run a job to restore from a database backup for every single module which should not have been stowed - sometimes over 20,000 modules.
e.g. as an ant run property -pMaxModules=25 or something would be extremely helpful and a failsafe if more than x modules change (or whatever number specified) abort the run
Thank you so much for this, really appreciated, while I cater for it now, will prevent an extra staged run in my pipeline.
Thanks
Hello Trentan,
In NaturalONE version 9.3.2 we added new functionality that will allow you to influence the list of effected modules, please see documentation:
https://documentation.softwareag.com/one/9.3.2/en/webhelp/one-webhelp/core/using/use-deploy-nat.htm#use-deploy-nat-user-exits-handling
This will allow you to check the list of affected modules and if it is larger than e.g. 25 set the all/some to not-affected.