-
Notifications
You must be signed in to change notification settings - Fork 7
add definitions.md #53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
This commit adds the foundation for definitions to give a common semantics across the various concepts within the SDLC. This commit explicitly starts with 'build'. Signed-off-by: xibz <[email protected]>
✅ Deploy Preview for cdevents ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
In reference to cdevents/spec#253 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
WIP, more comments on the way
| Docker Registry | Stores and manages Docker container images | | ||
| Git/GitHub/GitLab| Version Control Systems that store source code and its history | | ||
| Amazon S3/Azure Blob Storage/GCS | Object storage services used for archiving logs, backups, or raw data | | ||
| Kubernetes | Can store configuration via ConfigMaps/Secrets, but not typically "artifacts" | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would push against the idea of Kube as a store. It is an anti-pattern to rely on Kube ConfigMaps/Secrets for durable storage. Typically "ConfigMaps/Secrets" are simply the add-on data to assist Kube to accomplish its scheduling / declarative-state tasks.
run a system. These include: | ||
|
||
- **Static assets**: images, fonts, CSS, markdown | ||
- **Configuration files**: YAML, JSON, XML, `.env` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Terraform/CloudFormation etc.. ?
|
||
This document defines common concepts and ideas used across the SDLC (software | ||
development lifecycle). By establishing a shared vocabulary, it ensures that | ||
tools leveraging CDEvents use a consistent language and adhere to common |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you want to link back to the cdevents spec?
- CD ..
- CI ...
- Testing ..
- Operations ...
|
||
## 🏗️ Build | ||
|
||
A **build** is the automated process of transforming **source code** and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reference cdevents spec of build
?
Related CDEvents for Builds
- 🏷️ **Versioning**: tagging or stamping artifacts | ||
- 🧪 **Static analysis** *(pre-build or during build)* | ||
- 🧬 **Configuration templating**: injecting environment-specific variables | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SBOM?
Helm/Kustomzie?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Manifest rendering
Artifact signing
@@ -0,0 +1,208 @@ | |||
# CDEvents Concepts and Definitions | |||
|
|||
This document defines common concepts and ideas used across the SDLC (software |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the introduction, highlight that this is meant to be used as a dictionary
This commit adds the foundation for definitions to give a common semantics across the various concepts within the SDLC.
This commit explicitly starts with 'build'.
I wanted to first create the page, and once we agree we can figure out where to best link it from