dont rebuild extensions for test infra updates

未关闭
  • 哪里不对？
#403 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
55/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
docker, github-actions, go
领域
build-system, ci-cd

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Go
星标
58
派生
43
平均合并
1 天 10 小时
30 天内合并 PR
27

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

cloudnative-pg/postgres-extensions-containers 的其他 Issue

查看 cloudnative-pg/postgres-extensions-containers 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。