Entry Points

CDAF Entry Scripts

CDAF providers 4 entry scripts for different purposes.

  • ci : Build and Package only, i.e. Continuous Integration, mandatory argument is BUILDNUMBER
  • cd : Release, i.e. Continuous Delivery or Deploy (depending on gating or not), mandatory argument is ENVIRONMENT
  • cdEmulate : Executes ci and then cd, generates BUILDNUMBER if not supplied and uses configurable ENVIRONMENT
  • entry : Executes ci and then cd, generates BUILDNUMBER if not supplied and uses configurable ENVIRONMENT(s)

Continuous Integration (CI)

The CI entry point (ci.bat/ci.sh) will perform the build and package process. Recommended configuration is to produce a self extracting deployable artefact (release.ps1/release.sh).

sequenceDiagram ci ->>+ buildPackage: BUILDNUMBER buildPackage ->>- ci: release

Continuous Delivery/Deploy (CD)

See self-extracting release.

CD Emulation

The CD Emulation (cdEmulate.bat/cdEmulate.sh) is a simple wrapper which performs the CI process, and then executes the CD process, using the configured or default environment.

sequenceDiagram cdEmulate ->>+ buildPackage: BUILDNUMBER buildPackage ->>- cdEmulate: release cdEmulate ->>+ release: ENVIRONMENT release ->>- cdEmulate: deployment results

Entry

The entry wrapper (entry.bat/entry.sh), similar to cdEmulate, performs the CI process and CD process. The CD process however supports additional, optional, configuration for releases based on branch name (substrings).

sequenceDiagram cdEmulate ->>+ buildPackage: BUILDNUMBER buildPackage ->>- cdEmulate: release loop for each matching branch name cdEmulate ->>+ release: ENVIRONMENT release ->>- cdEmulate: deployment results end