Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to deal with disappear-y packages #35

Open
leoluk opened this issue Jan 30, 2023 · 3 comments
Open

How to deal with disappear-y packages #35

leoluk opened this issue Jan 30, 2023 · 3 comments

Comments

@leoluk
Copy link
Contributor

leoluk commented Jan 30, 2023

Fedora mirrors tend to remove outdated packages relatively quickly. Is there an established workflow for caching those to a mirror?

@leoluk leoluk changed the title How to deal with disappear-y dependencies How to deal with disappear-y packages Jan 30, 2023
@rmohr
Copy link
Owner

rmohr commented Jan 30, 2023

We have a generic tool in kubevirt: https://github.com/kubevirt/project-infra/tree/main/robots/cmd/uploader. It uploads all our dependencies to gce.

In general it is multi-layered:

  • the upload tool adds the RPMs to gce
  • Inside our CI we have a bazel greenhouse cache which stores them as well, to not always go to GCE

@leoluk
Copy link
Contributor Author

leoluk commented Feb 1, 2023

This obscure downloader feature could be an option to avoid the WORKSPACE rewriting: https://blog.aspect.dev/configuring-bazels-downloader

@rmohr
Copy link
Owner

rmohr commented Feb 1, 2023

This obscure downloader feature could be an option to avoid the WORKSPACE rewriting: https://blog.aspect.dev/configuring-bazels-downloader

That is a nice option. In general I like having them in the workspace, since that reflects where they are, and allows easy checking based on the WORKSPACE that dependencies are indeed mirrored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants