Publish same package to multiple repositories #342

New Issue

Jef Roosens · 2023-01-27T08:30:49+01:00

Jef Roosens commented

2023-01-27 08:30:49 +01:00

The usecase for this would be creating specialized repositories (e.g. a Vieter repository), while still using my main bur repository for all my packages. Instead of building these packages twice, and adding a target once for each repository, a target could instead specify multiple repositories, with the resulting packages being published to each of these repositories. This could be achieved by moving the uploading of built package archives to a separate API route.

Now that I think of it, if we're moving this to another API route, we might as well change it so an agent doesn't need to know what repository it needs to publish a package to. It could simply provide the job ID, and the server would know where the packages should go.

The usecase for this would be creating specialized repositories (e.g. a Vieter repository), while still using my main `bur` repository for all my packages. Instead of building these packages twice, and adding a target once for each repository, a target could instead specify multiple repositories, with the resulting packages being published to each of these repositories. This could be achieved by moving the uploading of built package archives to a separate API route. Now that I think of it, if we're moving this to another API route, we might as well change it so an agent doesn't need to know what repository it needs to publish a package to. It could simply provide the job ID, and the server would know where the packages should go.

Jef Roosens added the

Idea

label 2023-01-27 08:30:49 +01:00

Sign in to join this conversation.