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

Create a new table for storing Scorecard metrics #2668

Open
1 of 2 tasks
Tracked by #434
mayaCostantini opened this issue Aug 2, 2022 · 2 comments
Open
1 of 2 tasks
Tracked by #434

Create a new table for storing Scorecard metrics #2668

mayaCostantini opened this issue Aug 2, 2022 · 2 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance.

Comments

@mayaCostantini
Copy link
Contributor

mayaCostantini commented Aug 2, 2022

This issue is part of the following EPIC: thoth-station/core#434

2. Compute metrics for packages present in Thoth's database that will serve as a basis for a global software stack quality score

Taking the example of OSSF Scorecards, we already aggregate this information in prescriptions which are used directly by the adviser. However, the aggregation logic present in prescriptions-refresh-job only updates prescriptions for packages already present in the repository. We could either aggregate Scorecards data for more packages using the OSSF BigQuery dataset or have our own tool that computes Scorecards metrics on a new package release, which could be integrated directly into package-update-job for instance. This would most likely consist in a simple script querying the GitHub API and computing the metrics on the project's last release commit.

Create a new table in storages for storing those metrics

For the corresponding ADR proposal on how to aggregate the Scorecard data, see thoth-station/core#439

Next steps:

  • Validate the ADR proposal
  • Create a new database table with package name, version and columns for Scorecard checks
@sesheta sesheta added the needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. label Aug 2, 2022
@sesheta
Copy link
Member

sesheta commented Aug 2, 2022

@mayaCostantini: This issue is currently awaiting triage.
If a refinement session determines this is a relevant issue, it will accept the issue by applying the
triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@mayaCostantini mayaCostantini changed the title Create a new table in storages for storing those metrics Create a new table in storages for storing Scorecard metrics Aug 2, 2022
@mayaCostantini mayaCostantini changed the title Create a new table in storages for storing Scorecard metrics Create a new table for storing Scorecard metrics Aug 2, 2022
@mayaCostantini mayaCostantini added sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. and removed needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. labels Aug 2, 2022
@mayaCostantini mayaCostantini transferred this issue from thoth-station/core Aug 2, 2022
@goern
Copy link
Member

goern commented Aug 8, 2022

/kind feature

@sesheta sesheta added the kind/feature Categorizes issue or PR as related to a new feature. label Aug 8, 2022
@codificat codificat moved this to 🆕 New in Planning Board Sep 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance.
Projects
Status: 🆕 New
Development

No branches or pull requests

3 participants