dont rebuild extensions for test infra updates

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

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
docker, github-actions, go
Área
build-system, ci-cd

Línea de trabajo

Start with the filters in bake.yml and trace how changes to test dependencies trigger extension builds on Renovate branches and main. Compare the issue’s options 2 and 3, then inspect the linked commit and comparison for existing approaches. Done means test builds still run for a selected subset of extensions on Renovate branches while test dependency updates no longer rebuild every extension.

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

Descripción

as the number of extensions grows, this will begin to consume more and more time from GH action workers. (i'm hitting this downstream.) a big contributor is updates to alpine, psql, kubectl, etc by renovate. these currently rebuild everything. but they are only used for test infra - they dont impact extension builds.

we should not rebuild the extension if we just change something in the testing dependencies.

option 1: if we want to remove all rebuilds (including tests on PR branches) then i think we can just add this to the filters in bake.yml

              - 'Taskfile.yml'
              - 'test/**'
              - 'dagger/maintenance/**'

option 2: we can let test builds run for all extensions on PR branches but not on main with [something like this]

option 3: on PR branches just [auto-build for a select few extensions]

to automerge these in the future there needs to be at least some kind of test.  so we need option 2 or 3

its only another couple LOC to do option 3 and run tests against a subset of extensions instead of everything (eg. pgaudit, pgvector, postgis)

i’m leaning toward doing just those three extensions on the renovate branches, so we dont blow up the GH runner backlog with jobs.

Lenguaje dominante
Go
Estrellas
58
Forks
43
Merge medio
1 d 10 h
PR fusionados (30 d)
27

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 cloudnative-pg/postgres-extensions-containers

Todos los issues de cloudnative-pg/postgres-extensions-containers

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.