Skip to main content
Version: Next

References

The references section provides detailed information on terminology and abbreviations used throughout the Pillars of Creation documentation. Understanding these terms is essential for effectively navigating the documentation and comprehending the concepts discussed.

Terminology and Abbreviations

Term/AbbreviationDefinition
PipelineA sequence of automated processes that compile, build, test, and deploy code.
JobA single task executed by a pipeline, such as code compilation or testing.
StageA collection of jobs that execute in a predefined order within a pipeline.
ArtifactA byproduct of the software development process, such as binaries, container images, or reports.
RunnerAn application that executes the jobs defined in a CI/CD pipeline.
RegistryA storage and content delivery system that holds named container images, available in different tagged versions.
GitLab Container RegistryA secure, private registry for storing container images within GitLab.
SBOM (Software Bill of Materials)A detailed list of components and dependencies within a software artifact.
BoE (Body of Evidence)Documentation and artifacts collected to demonstrate compliance and security posture.
PublishThe act of storing and making artifacts available in a registry or repository.
Static AnalysisExamination of artifacts without executing them, identifying potential issues through code inspection.
Dynamic AnalysisTesting artifacts during execution to find vulnerabilities that manifest in a running environment.
Vulnerability ScanAn automated process to identify security weaknesses within software artifacts.
CI/CD (Continuous Integration and Continuous Deployment)A methodology that emphasizes frequent integration of code changes and automated deployment.
HelmA package manager for Kubernetes that helps you define, install, and upgrade complex Kubernetes applications.
DependencyExternal code or libraries that a project relies on to function correctly.

Tools