1 year ago

To automate deployment processes, CI/CD needs context: deployment configurations, build configurations, artifacts, version numbers, dependencies, environment variables, test results and more. For example, deployment configurations might be stored in a separate YAML file, environment variables might be defined in a script or in the deployment manifest and version numbers might be tracked manually in a spreadsheet.

First Step: A Software Catalog That Can Store CI/CD Data

For example, within the deployment configurations category, there might be metadata items for the deployment target, the deployment strategy and the deployment version.

A software catalog with CI/CD metadata can create a single source of truth, solve version and security issues, and allow automation of deployment processes and more.