Support pacolo workflow #191

New Issue

Jef Roosens · 2022-05-21T12:08:22+02:00

Jef Roosens commented

2022-05-21 12:08:22 +02:00

Once the amount of repos increases, a Vieter build server will query the repositories a lot for packages. To decrease the load on those servers, I'd like to be able to use pacolo, a caching server for Pacman repositories. All Vieter operations could use a pacolo instance to request their packages, & the server will cache their requests accordingely. This is also prevents multiple builds from downloading the same dependency multiple times.

I'm not sure whether explicitely adding support for this caching server is useful, but perhaps adding general support for a long-living Docker container that all builds containers have access could be feasible.

Once the amount of repos increases, a Vieter build server will query the repositories a lot for packages. To decrease the load on those servers, I'd like to be able to use [pacolo](https://github.com/anatol/pacoloco), a caching server for Pacman repositories. All Vieter operations could use a pacolo instance to request their packages, & the server will cache their requests accordingely. This is also prevents multiple builds from downloading the same dependency multiple times. I'm not sure whether explicitely adding support for *this* caching server is useful, but perhaps adding general support for a long-living Docker container that all builds containers have access could be feasible.

Jef Roosens added the

idea

label 2022-05-21 12:08:22 +02:00

Jef Roosens commented

2022-05-21 14:12:15 +02:00

Poster

It might actually be even better to fork pacolo to more tightly integrate it with Vieter.