jilodallas.blogg.se - Define tagr

You set the repository filter to **, meaning that all repositories in the project are included.

Repositories B to E each have 7 artifacts with 1 untagged artifact, none of which have been pulled in the last month.

Repository A has 102 artifacts with 2 untagged, all of which have been pulled in the last week.

You have 5 repositories in a project, repositories A to E.

Use the checkbox to select whether untagged artifacts should be captured as part of the set of artifacts eligible for tag retention.įor information about how the ** wildcard is applied, see. Wild cards (for example *tag, tag*, and **) are permitted. You can identify tags that either have a certain name or name fragment, or that do not have that name or name fragment. Identify the tag or tags on which to apply the rule. Set which tags to retain either by specifying a maximum number of tags, or by specifying a maximum period for which to retain tags. No action is taken on the nonspecified repositories at this stage. The identified repositories are earmarked for further matching based on the tag criteria.

The repository filter is applied first to mark the repositories to which to apply the retention rule. Wild cards (for example *repo, repo*, and **) are permitted. You can identify repositories that either have a certain name or name fragment, or that do not have that name or name fragment. Identity the tags on which to apply the rule. The OR algorithm is used between rules.Ī tag retention rule has 3 filters that are applied sequentially, as described in the following table. Rather, when you set a rule, any tags in a repository that are not identified as being eligible for retention are discarded. You do not define rules to explicitly remove tags. As the name suggests, when you define a retention rule for a repository, you are identifying which tags to retain.

This allows for greater granularity when defining your retention rules. You define tag retention rules on repositories, not on projects. As a Harbor system administrator, you can define rules that govern how many artifacts of a given repository to retain, or for how long to retain certain artifacts. These excess artifacts can obviously consume large quantities of storage capacity. A repository can rapidly accumulate a large number of artifacts, many of which might not be required after a given time or once they have been superseded by a subsequent artifact build.