[MDBF-231] ci.mariadb.org save release branches packages separately Created: 2021-02-20 Updated: 2022-02-01 |
|
| Status: | Open |
| Project: | MariaDB Foundation Development |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Vicențiu Ciorbaru | Assignee: | Vlad Bogolin |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Currently, builds are stored together at ci.mariadb.org. When the disk becomes full, older builds are automatically deleted. This causes problems when a release is coming soon. It is possible that the release binaries end up getting deleted, before they are uploaded to the mirrors. To fix this problem, we should specialize saving particular branches separately and not delete the most recent n (let n be 5) builds for those branches. Those branches are:
|