Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Below is a list of some of the other stage descriptions:

  • promote-stash: When all of the mandatory stages for a pipeline succeed, the stashed artifacts are copied to the promoted-stash area of the bucket, and are available for other pipelines to use when they use the mock-build CI Build Configuration option. The linked promoted stash is for master, but each mainline development branch will have it's own area in the bucket, and the version used by mock-build depends on the target branch specified.
  • cross-upgrade-tests: Deploys old version of AM, creates some config, upgrades AM, and then verifies that the upgrade did the right thing (and did not fail)
  • elastic-federation-tests: Runs a set of functional tests that verifies that SAML SSO works in an elastic type deployment
  • file-smoke-tests: Deploys AM with a file based configuration
  • file-sts-tests: Deploys AM with a file based configuration
  • file-functional-tests: Deploys AM with a file based configuration
  • saml2-node-tests-compose: Runs Pyforge functional tests for the SAML2 authentication node
  • upgrade-tests-functional: Deploys old version of AM, upgrades it, then runs the functional smoke tests against the upgraded instance.
  • upgrade-tests-ui-admin: Deploys old version of AM, upgrades it, then runs the UI admin smoke tests against the upgraded instance.
  • upgrade-tests-ui-user: Deploys old version of AM, upgrades it, then runs the UI user smoke tests against the upgraded instance.
  • k8s: Run the Lodestar Kubernetes tests, using the stable ForgeOps branch + the AM commit in the current build
  • pit1: Run the Lodestar PIT1 tests, using the stable ForgeOps branch + the AM commit in the current build

...

  • mock-build: This will use a previous previously built version of openam instead of building one from the source, in master (7.0) currently mock-build=true is needed, otherwise there is groovy.lang.MissingMethodException: No signature of method: static. The version used will be from the promoted-stash of the target branch.
  • fast-mode: This will run a fast version of the stages supporting this options. This often boils down to running a subset of tests push-to-elasticsearch: This will push the tests result to elasticsearch staging index. This can be visualized in kibana. ( This will soon be available from the dashboard ). This is not supported by all stages.
  • stop-automatic-build: if set to true,  every every build triggered by an updated pull request will be aborted. ( You can still trigger a build manually by clicking the button in your PR)


Examples of custom build passed in the PR description are :

...