クリーンアップ

手動クリーンアップ起動

サーバーのクリーンアップ設定の前回のクリーンアップセクションでは、以下のことが可能です。

• Review the information on the previous server clean-up date and duration helping you decide whether to launch the clean-up process at a given moment.

• Run clean-up manually using the 今すぐクリーンアップを開始 button.

During clean-up, TeamCity reports the progress. If you need, you can stop the clean-up process, and the remaining data will be removed during the next clean-up.

Base Rule

A single base rule is assigned to each project or build configuration. With a base rule, you can define a number of successful builds to preserve, and/or the time period to keep builds in the history.

The following clean-up levels are available in a base rule:

• 成果物 : all data including build logs is preserved; hidden artifacts are also preserved.

• ヒストリー : all the build data is deleted except for builds statistics values that are visible in the statistics charts.

• すべて : no build data remains in TeamCity.

Each level includes those listed above it.

By default, everything is kept forever. When you select custom settings, for each of the levels above you can specify:

• Number of days :
  Builds older than the number of days specified will be cleaned with the specified level. The starting point is the date of the last build, not the current date. A day is equivalent to a 24-hour period, not a calendar day.

• Number of successful builds :
  Only builds older than the last matching successful build will be cleaned with the level specified (all the failed builds between the preserved successful ones are kept). This rule is only taken into account if there are successful builds in the build configuration.

When both conditions are specified, only the builds, which must be cleaned according to all applied rules and not preserved by keep rules, will be actually removed: TeamCity finds the oldest build to preserve according to each of the rules and then cleans all builds older than the oldest one of the two found.

For the 成果物 level you can also specify the patterns for the artifact names: the artifacts matching the specified pattern will be in- or excluded from the clean-up. Use newline-delimited rules following Antのようなパターン(英語) . For example:

• To clean-up artifacts with file as a part of the name, use the following syntax: +:**/file*.* .

• To exclude *.jar artifacts with file as a part of the name from clean-up, use -:**/file*.jar .

Keep Rule

A keep rule defines what particular data to preserve during the clean-up. Multiple keep rules can be assigned to a project or build configuration.

In each keep rule, you can configure the following settings:

• 保存するデータを作成する : 履歴、アーティファクト、ログ、統計、またはすべて。

• To keep artifacts in dependencies or not. This option controls if the builds of the dependency build configurations are also cleaned up. With this option enabled, if some build is preserved by this rule, all artifacts of its dependency builds will also be preserved. The option works similarly to the 依存関係 option of a base rule.

• ビルド範囲 : ルールの影響を受ける時間間隔または最後のビルドの数。

• Optionally, you can filter the preserved builds by their status, tags, and branches. You can also restrict the rule only to personal or non-personal builds.

• Choose if the limits must be applied to each matching branch individually or to all the builds in the selected branches as a single set.
  This condition applies once per each affected build configuration. If no branches are specified in the filter, it applies as follows: either to each branch in a build configuration or to all the build configuration branches as a set.
  Example: if you select to keep statistics of 10 last builds and choose two branches for this rule, you can either choose " All selected " to preserve 10 last builds among both selected branches or choose " Each selected branch " to preserve 20 last builds – 10 for each of the branches.

TeamCity processes a keep rule in the following order:

1. フィルター the builds of the affected project or build configuration.

2. Determines if the rule will apply to all selected branches or to builds in each selected branch individually (see description).

3. Keeps builds only in a specified range.

4. Determines what types of build data to preserve.

5. Determines if the artifacts for the dependency builds must be preserved.

Notes on the keep rule behavior:

• If several tags are entered, the rule will apply to all builds marked with any of these tags.

• In all " Days since... " range options, TeamCity doesn't consider fractional hours of a certain date and applies a rule only to builds that started in a time interval from the selected day (from midnight until 11:59 PM) and back to the starting day of the affected range (the selected day minus the configured limit of days).