Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Trigger hardware registry imports on repository updates

Abierto
  • ¿Algo no está bien?
#2,191 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github-actions, python
Área
backend, devops

Línea de trabajo

Start by locating the existing hardware registry import command in the Dashboard and the cron job that invokes it; then inspect how the kernelci-pipelines repository stores the registry YAML and configures GitHub Actions. The issue is done when updates to that file on main trigger a secure, retryable import, report failures, and prevent overlapping or stale imports from corrupting newer data.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Backend
Description

Currently, the Dashboard periodically imports the hardware registry from the kernelci-pipelines repository using a cron job. This process downloads the YAML file and updates the Dashboard database, even when the file hasn't changed.

We could replace this periodic polling mechanism with an event-driven approach using GitHub Actions.

Proposed solution

When changes to the hardware registry YAML file are merged into the main branch of kernelci-pipelines, a GitHub Actions workflow should trigger the import process on the Dashboard server.

The workflow should:

  1. Run only when the hardware registry YAML file is updated on main.
  2. Securely connect to the Dashboard server.
  3. Execute the existing import management command to update the database.
  4. Report whether the import succeeded or failed.
Benefits
  • Faster updates: Hardware registry changes are reflected in the Dashboard shortly after being merged.
  • Reduced unnecessary work: Imports only run when the registry changes.
Caveats
  • Idempotency: The import command should be safe to execute multiple times for the same registry version, without creating duplicate or inconsistent data.
  • Concurrency: Multiple updates may trigger overlapping imports. We should ensure that concurrent executions do not interfere with each other.
  • Out-of-order execution: GitHub Actions workflows are not guaranteed to execute in the order they were triggered. An older import could finish after a newer one and overwrite the latest registry data. We should ensure that stale imports cannot overwrite newer data.
  • Failure recovery: Failed imports should be easy to retry, ideally through a manually triggered workflow, without compromising data consistency.
Acceptance criteria
  • A GitHub Actions workflow in kernelci-pipelines triggers when the hardware registry file changes on main.
  • The workflow securely triggers the import command on the Dashboard server.
  • Import failures are reported.
  • The import process remains safe to retry in case of failures.
  • The import command can still be invoked manually if necessary
Lenguaje dominante
Python
Estrellas
10
Forks
32
Merge medio
3 d 36 min
PR fusionados (30 d)
23

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de kernelci/dashboard

Todos los issues de kernelci/dashboard

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.