[Refactor][CircleCI] Make extractJobs and extractWorkflows incremental with NewStatefulApiExtractor

Abierto
  • ¿Algo no está bien?
#9,305 0 comentarios 1 reacción 1 asignado Ver en GitHub

Los mantenedores suelen responder en 2 días

@zahorniak ya está trabajando en esto.

Desde el 2/11/2026.

  • #9313 de @zahorniak — abierto

Evaluación

Este issue todavía no se ha evaluado.

Descripción

What and why to refactor

The CircleCI extractors extractJobs and extractWorkflows use the old api.NewApiExtractor. This extractor reads all rows of the raw table on every run, also on incremental runs. The GitHub, GitLab, Jira and YouTrack plugins already use api.NewStatefulApiExtractor, which reads only the raw rows added since the last successful run.

So the time for each run grows with the size of the raw table, not with the new CI activity. In our instance:
_raw_circleci_api_jobs about 9.3M rows (10.3 GB)
New raw rows per night about 166k (almost all from the problem in #9304)
extractJobs speed about 490 rows/s with default MySQL settings
extractJobs time per run about 4.5 hours for one project, every night

The job extraction writes one row per commit. It uses almost no CPU on the DevLake or MySQL side; the disk sync on each commit sets the speed.

Environment: DevLake v1.0.3-beta14 (the code is the same on main at 351d86738), MySQL 8.4, CircleCI Cloud, nightly incremental blueprint.

Describe the solution you'd like

Change ExtractJobs (backend/plugins/circleci/tasks/job_extractor.go) and ExtractWorkflows (backend/plugins/circleci/tasks/workflow_extractor.go) to api.NewStatefulApiExtractor, the same way as other plugins (for example backend/plugins/github/tasks/pr_extractor.go).

  • On an incremental run, the extractor reads only raw rows with created_at >= since.
  • On a full sync, or when the configuration changes, it reads all raw rows, as it does now.
  • Duplicate raw rows for the same job are safe: the tool-layer key is (connection_id, workflow_id, id) for jobs and (connection_id, id) for workflows, so a newer row replaces the older one.
  • Add or update the e2e tests for the two extractors.

With #9304 fixed and this change, extractJobs in our instance would read about 20k rows per night, not 9.3M.

I can start work on a PR for this if the DevLake maintainers approve this approach.

Related issues

  • #9304: the "unfinished details" collectors collect the same jobs again without a limit.
  • #8907, #8956: earlier fixes in the same collectors.

Additional context

A one-time cleanup of the duplicate raw rows is not part of this change. After both fixes, a full sync removes the old raw rows.

Lenguaje dominante
Go
Estrellas
3.2k
Forks
832
Merge medio
1 d 21 h
PR fusionados (30 d)
78

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

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 apache/devlake

Todos los issues de apache/devlake

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.