test/data/manifests: regenerate to drop build packages
With the more fine-grained build package set, different images will use different build pipelines and each of them will be smaller. We don't currently cache build pipelines so there is no downside to this. Even when we start caching the difference between having one build pipeline per image and one shared one is minimal at scale. This will still benefit users doing one-off builds on-prem. Most importantly, this tracks things correctly, making pipelines more composable without having to maintain a global list of dependencies.
This commit is contained in:
parent
fa7d2f2647
commit
6ae65f1951
69 changed files with 263 additions and 43724 deletions
File diff suppressed because it is too large
Load diff
Loading…
Add table
Add a link
Reference in a new issue