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.
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
mainbranch 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