homelab/stack
1
0
Fork 0
Code Issues 123 Pull Requests 2 Actions Packages Projects 1 Releases Wiki Activity

pkg-mirror-sync: CI pipeline to refresh mirrors from inventory #163

New Issue
Closed
opened 2026-03-24 03:54:38 +00:00 by kert · 0 comments
kert commented 2026-03-24 03:54:38 +00:00
Owner
Copy Link

Goal

A CI pipeline step that re-runs the inventory scanner, diffs against current mirror contents, and updates mirrors when packages change.

Scope

  • Pipeline triggers on changes to Dockerfiles, pyproject.toml, uv.lock, CI workflows
  • Runs pkg_inventory.py to regenerate manifest
  • Compares new manifest vs current mirror contents
  • Adds new packages to mirrors, flags removed packages
  • Works with Gitea Actions, Woodpecker, and GitHub Actions (CI-agnostic definition)
  • Pipeline definition in dev/pipelines/pkg-sync.yml (abstract) + per-CI adapters

Acceptance

  • Adding a new apt-get install foo to a Dockerfile triggers mirror update
  • Removing a package flags it for cleanup
  • Pipeline runs on all three CI backends
## Goal A CI pipeline step that re-runs the inventory scanner, diffs against current mirror contents, and updates mirrors when packages change. ## Scope - Pipeline triggers on changes to Dockerfiles, pyproject.toml, uv.lock, CI workflows - Runs `pkg_inventory.py` to regenerate manifest - Compares new manifest vs current mirror contents - Adds new packages to mirrors, flags removed packages - Works with Gitea Actions, Woodpecker, and GitHub Actions (CI-agnostic definition) - Pipeline definition in `dev/pipelines/pkg-sync.yml` (abstract) + per-CI adapters ## Acceptance - [ ] Adding a new `apt-get install foo` to a Dockerfile triggers mirror update - [ ] Removing a package flags it for cleanup - [ ] Pipeline runs on all three CI backends
kert added this to the P21: Package Supply Chain — inventory, mirrors, drift, vuln scanning milestone 2026-03-24 03:54:38 +00:00
kert added the cipipeline:ci labels 2026-03-24 03:54:38 +00:00
kert closed this issue 2026-03-24 04:35:00 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
REST API (FastAPI)
 auth
Authentication and authorization
 bib
Bibliography, Zotero, citations
 ci
CI/CD pipelines and Woodpecker plugins
 cli
CLI commands and UX
 cloud
Cloud provider abstraction (AWS, GCP, Azure, self-hosted)
 config
Configuration and wiring
 data
Data loading, CCLF, BCDA, seeds
 databricks
Databricks jobs and deployment
 docs
Documentation and generated references
 image:api
image:docs
image:mc
image:notebooks
image:zotero
infra
lakehouse
Nessie, Polaris, Trino, Iceberg
 llm
llm module — local RAG over comments + Zotero corpus
 notebooks
marimo notebook errors (auto-filed by nb-watcher/nb-integration)
 packaging
Python packaging, optional deps, build system
 pfs
pipeline
Pipeline execution and validation
 pipeline:ci
pipeline:deploy
pipeline:harden
pipeline:infra-ci
pipeline:rebuild-all
pipeline:release
qpp
quality
Testing, coverage, error handling
 step:build
step:deploy
step:hadolint
step:lint
step:publish
step:scan
step:test
step:validate
styles
Charts, figures, visual theming
 tree
Project directory structure and file organization
No Label ci pipeline:ci
Milestone
No items
No Milestone P21: Package Supply Chain — inventory, mirrors, drift, vuln scanning
Projects
Clear projects
No project
Assignees
Clear assignees
kert renovate-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: homelab/stack#163
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?