Specify per-project archiver
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Capomastro |
Triaged
|
High
|
Unassigned | ||
Bug Description
Currently only one archiver can be set as the default, and this is a bit misleading because only one is used; so a more accurate name would be "active" archiver.
In any case, it would be useful if a project could specify which archiver to use, from the ones available. The use case is publishing each project to a different place (for instance, project A wants to SSH publish to our sytem-image-server directly but project B wants to SSH publish to another, intermediate server to do some postprocessing prior to image publication and project C wants to Swift publish to a different location).
So project could have a relation with archive and use that to store its artifacts. If no archive is explicitly selected, *then* it defaults to the one marked as "default archiver".
| Changed in capomastro: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 2015-05 |
| Caio Begotti (caio1982) wrote | #1 |
| Changed in capomastro: | |
| milestone: | 2015-05 → future |
Falling back to the default archiver would be needed for dependencies builds too (Capomastro will use this automatically if the archiver is set to be this "active" one anyway). Just wanted to comment on that because we probably don't want to overcrowd the dependencies screens with archivers option; only projects matter in this case.