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

Review data storage policy (and format) #76

Open
jmMeessen opened this issue Jun 20, 2024 · 0 comments
Open

Review data storage policy (and format) #76

jmMeessen opened this issue Jun 20, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@jmMeessen
Copy link
Contributor

What feature do you want to see added?

This application, still in the exploration phase for what data to extract, has evolved in an iterative way. Some parts are less then optimum by choice. The data storage is one of them: data is stored has been simplified. It is based on CSV or MarkDown files stored in the Git Repository itself.

The migration from a private (lab) environment to a public community organisation (jenkins-infra) has shown these short comings. In order for the daily "Honored Contributor" automated extraction to work, the main branch had be left unprotected. Which is not a recommended pattern and not part of the jenkins-infra policies.

The data storage policy should be reviewed, alternative strategies proposed, and implementation prioritized.

cc: @gounthar @lemeurherve

Upstream changes

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant