mirrormanager SOP should include post-release cleanup of old artifacts when vaultin #27
Labels
No Label
bug
component/ansible
component/git
component/idm
component/mattermost
component/mirrors
duplicate
effort
high
effort
low
effort
medium
enhancement
gain
high
gain
low
gain
medium
help wanted
invalid
issue
needinfo
permissions
priority
high
priority
low
priority
medium
task
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/meta#27
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
tl;dr -
we run scan-primary-mirror w/o --delete-directories normally to save time and because we have no reason to delete things unnecessarily during the course of a Z stream.
When we release a new X.Y, we need to use --delete-directories in order to remove orphaned directories causing slowdowns in syncing for HostCategoryDirectories that don't actually exist.