Upstream package cache for CI

CI jobs are sensitive to package registry availability and policy changes. Ravenstash upstream read-through lets a private repository resolve configured upstream misses while keeping installs behind Ravenstash authentication.

Why use it

• CI uses one private repository URL.
• Package access remains tied to Ravenstash customer credentials.
• Warm upstream artifacts can be served from Ravenstash-managed remote storage.
• The dashboard exposes remote-cache package and artifact visibility.

What it is not

It is not a public mirror, anonymous cache, or bulk-preseed system. Current cache population is bounded and driven by private repository access.

Rollout pattern

Start with one repository and one CI pipeline. Confirm the package manager resolves private packages first, then configured upstream misses. After validation, move more pipelines to the same Ravenstash repository URL.