Child pages
  • fbc-config-upgrader-tests

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Re-worded summary sections for clarity. Removed user-specific path.

tl;dr

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.

Background/Purpose

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.

See 

Jira
serverForgeRock JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId45b4e541-fe03-30e2-b999-cf4e643b93ec
keyAME-18809
 for the implementation.

...

Code Block
languagebash
themeEmacs
titledocker-compose
$ 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

...