Skip to content
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

What will be the storage mechanism for build instructions and results? #4

Open
Klaven opened this issue Jan 30, 2023 · 1 comment
Open
Milestone

Comments

@Klaven
Copy link
Contributor

Klaven commented Jan 30, 2023

I'm thinking in terms of the part of the system that manages everything, how will it store for instance that the latest build of the null web succeeded and was deployed on datetime using git hash xyz?

Sqlite for starters, Postgres, something else?

@RussellWaite RussellWaite changed the title What wil be the storage mechanism for build instructions and results? What will be the storage mechanism for build instructions and results? Jan 30, 2023
@Klaven Klaven added this to the PoC milestone Feb 8, 2023
@salasberryfin
Copy link

Hey @Klaven!

Is it necessary to use a relational DB? If it's only used to store general build information, would you consider using a key-value store, instead? I always like to go for the non-relational option unless I have specific constraints that require a relational model.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants