Pipeline stage to test that AM's FBC (file-based config upgrades successfully ) can be upgraded (and then used with AM successfully) after every commit. If it fails it is likely an update to the This stage will fail if required openam-config-upgrader rules is required in are missing from fbc/master.groovy.
Deployments of AM (FBCfile-based) AM require an upgrade mechanism. The openam-config-upgrader (released within the AM.zip) can upgrade these the FBC configuration files. To ensure that the upgrader rules are kept up to date the fbc-config-upgrader-tests stage has been added to the postCommit pipeline. The premise is that a known baseline FBC can be upgraded, using the tool and rules, and then used to successfully start up the latest version of AM. The rules should be idempotent; so running multiple times will have produce the same end result.
$ pwd /Users/aczvuser/GITgit-repo/openam/jenkins-scripts/docker/centos7 $ COMMAND="functional-tests --groups and\(and\(or\(idrepo,smoke\),not\(ssoadm\)\), not\(mock-server\)\)" docker-compose -f docker-compose.yml -f docker-compose.overrides.fbc-upgrade.yml up