# Manage artifacts and repositories

> Manage artifacts and repositories - Registry views for browsing, adding, and managing artifacts.

This Markdown file sits beside the HTML page at the same path (with a `.md` suffix). It summarizes the topic and lists links for tools and LLM context.

Companion generated at `2026-07-30T11:40:01.815256+00:00` (UTC).

## Primary page

- [Manage artifacts and repositories](https://docs.datarobot.com/ja/docs/workload-api/build-artifacts/artifact-ui.html.md): Full documentation for this topic (Markdown sidecar).

## Sections on this page

- [Navigate the service artifact page](https://docs.datarobot.com/ja/docs/workload-api/build-artifacts/artifact-ui.html.md#navigate-the-service-artifact-page): In-page section heading.
- [Add a new service artifact](https://docs.datarobot.com/ja/docs/workload-api/build-artifacts/artifact-ui.html.md#add-a-new-service-artifact): In-page section heading.
- [Perform artifact actions](https://docs.datarobot.com/ja/docs/workload-api/build-artifacts/artifact-ui.html.md#perform-artifact-actions): In-page section heading.
- [テストワークロードの設定](https://docs.datarobot.com/ja/docs/workload-api/build-artifacts/artifact-ui.html.md#configure-test-workload): In-page section heading.
- [Manage service artifact configuration](https://docs.datarobot.com/ja/docs/workload-api/build-artifacts/artifact-ui.html.md#manage-service-artifact-configuration): In-page section heading.
- [Assemble a service artifact](https://docs.datarobot.com/ja/docs/workload-api/build-artifacts/artifact-ui.html.md#assemble-a-service-artifact): In-page section heading.
- [Review containers](https://docs.datarobot.com/ja/docs/workload-api/build-artifacts/artifact-ui.html.md#review-containers): In-page section heading.
- [環境変数の設定](https://docs.datarobot.com/ja/docs/workload-api/build-artifacts/artifact-ui.html.md#configure-environment-variables): In-page section heading.
- [Configure probes](https://docs.datarobot.com/ja/docs/workload-api/build-artifacts/artifact-ui.html.md#configure-probes): In-page section heading.
- [View the service artifact info](https://docs.datarobot.com/ja/docs/workload-api/build-artifacts/artifact-ui.html.md#view-the-service-artifact-info): In-page section heading.
- [View the Workload and endpoint](https://docs.datarobot.com/ja/docs/workload-api/build-artifacts/artifact-ui.html.md#view-the-workload-and-endpoint): In-page section heading.

## Documentation content

The Registry is where artifact lifecycle work happens: tracking which Workloads run a given artifact, assessing impact before replacing a locked artifact, and confirming that production Workloads reference locked artifacts. For the underlying model—types, lifecycle, repositories, and configuration layering—see [Artifact concepts](https://docs.datarobot.com/ja/docs/workload-api/build-artifacts/artifacts-concepts.html.md).

## Navigate the service artifact page

The Service artifact repositories page, accessed from Registry > Services, is the entry point for browsing all of an organization's artifacts. From the list on the resulting Service artifact repositories page, click a row in the Repository column to open its artifact list.

Each repository's list has separate tabs for Locked and Draft artifacts, with Status, Creation date, and Last modified columns. The two statuses differ in how many Workloads each can back:

| Artifact status | Active Workloads |
| --- | --- |
| ドラフト | At most one Workload. |
| ロック | Multiple Workloads supported. |

To locate a specific artifact, use Filters and Search in the top left corner of the page.Filters includes Created by and Tags fields.

## Add a new service artifact

Artifact creation is API-first: the Console exposes the REST call so you can copy it into a script or terminal and customize the payload. In the top right corner of the Service artifact repositories page, click + Add service artifact to open the Add new artifact panel. The panel shows a copy-ready code example for creating a simple draft artifact.

The example posts a JSON payload to `/api/v2/artifacts/` with a Bearer-token header to create an artifact in `draft` status. The payload supplies the artifact name and description, then defines container topology under `spec.containerGroups[].containers[]` —image URI, port, the `primary` flag, environment variables as name/value pairs, an entrypoint command array, and a readiness probe (path, port, initial delay, period, timeout). Adapt the payload to your container before running the request.

> [!TIP] Copy the example
> Click the Copy to clipboard button in the top right corner of the panel to copy the full example.

## Perform artifact actions

Each artifact and repository exposes a small set of lifecycle and governance actions. Which actions appear depends on the artifact's current status—the platform hides actions that would conflict with `draft` or `locked` rules.

Opening a repository and selecting an artifact opens the artifact detail view, which displays the Assemble tab. From there, the action buttons ( Test, Stop, Lock, Deploy) and the actions menu () are available on every tab.

> [!NOTE] Artifact and repository deletion
> Artifact repositories cannot be deleted if they contain locked artifacts or artifacts in use by Workloads. Artifacts cannot be deleted if they are locked or in use by Workloads.

For a service artifact repository, the actions menu () next to the repository name provides the following actions:

| アクション | 説明 |
| --- | --- |
| Share | Share the artifact repository with other users. |
| Delete | Delete the artifact repository and all artifacts in it. |

For a service artifact, the available action buttons depend on whether it's Draft or Locked:

| アクション | 説明 | ステータス |
| --- | --- | --- |
| Test | Run the draft service artifact for testing. Either manually stop the test, or the Workload automatically expires after 8 hours. サービスアーティファクトがワークロードに関連付けられていない場合、テストアクションを実行すると、テストを実行ダイアログが開きます。 このアーティファクトの実行中のワークロードを使用するには、ワークロードタブを開いてエンドポイントにアクセスするか、コンソールのワークロードを新しいタブで開きます。 | ドラフト |
| Stop | Stop the service artifact. | ドラフト |
| ロックする | Lock the service artifact without creating a Workload. | ドラフト |
| デプロイ | For a draft, locks the artifact and creates a Workload from it. For a locked artifact, creates a new Workload. | Draft or Locked |
| Actions menu |  |  |
| Share | Share the service artifact with other users. | Draft or Locked |
| Delete | Delete the service artifact. | ドラフト |
| Clone | Clone the service artifact. | ロック |

> [!NOTE] Artifact actions availability
> From the actions menu () next to the artifact in the Service artifact repositories page table, you can only access Share, Delete, and Clone actions. The Test, Stop, Lock, and Deploy actions are only available from the opened artifact detail view.

### テストワークロードの設定

テスト アクションは、テストのためにドラフトのサービスアーティファクトを実行します。 サービスアーティファクトがすでにワークロードに関連付けられている場合、 テスト アクションでは既存のワークロードが実行されます。 サービスアーティファクトがワークロードに関連付けられていない場合、 テスト アクションを実行すると、 テストを実行 ダイアログが開き、 リソースバンドル 、 スケーリング設定 、および レプリカ数 を設定できるようになります。

このアーティファクトの実行中のワークロードを使用するには、 [ワークロードタブを開いて](https://docs.datarobot.com/ja/docs/workload-api/build-artifacts/artifact-ui.html.md#view-the-workload-and-endpoint) エンドポイントにアクセスするか、コンソールのワークロードを新しいタブで開きます。

## Manage service artifact configuration

The artifact detail view is organized into three tabs, scoped from definition to deployment:

| タブ | 説明 |
| --- | --- |
| アセンブル | Review the artifact's containers, environment variables, and probes. |
| 情報 | Review identity and metadata for the artifact. |
| ワークロード | Review the Workload and endpoint associated with the artifact. |

### Assemble a service artifact

The Assemble tab defines the artifact and groups its components into three sections:

| セクション | 説明 |
| --- | --- |
| コンテナ | The artifact's containers and their Image URIs. |
| 環境変数 | The artifact's environment variables, with controls to add, edit, or delete. |
| プローブ | The artifact's readiness, liveness, and startup probes. Probes are used to check if the container is running and healthy. The path of a probe is required; other unfilled fields receive default values. |

### Review containers

The Containers section lists every container in the artifact along with its Image URI. Use this section to confirm what the artifact runs before locking or deploying.

### 環境変数の設定

The Environment variables section displays each variable's Name, Type, Value, and Field, with controls to add, edit, or delete.

| コントロール | 説明 |
| --- | --- |
| 編集 | Edit the Value of one or more environment variables, or click to delete them. |
| + Add environment variable | Open the Add environment variable dialog to define a new variable with Name, Type, and Value. |

For when to put values on the artifact vs. on the Workload runtime, see [Configuration layering](https://docs.datarobot.com/ja/docs/workload-api/build-artifacts/artifacts-concepts.html.md#configuration-layering).

### Configure probes

The Probes section displays the artifact's readiness, liveness, and startup probes. Probes are used to check if the container is running and healthy. The path of a probe is required, and other unfilled fields receive default values.

| Probe type | 説明 |
| --- | --- |
| Liveness | Checks whether the container is still healthy. If it fails too many times in a row, the container is automatically restarted. |
| Readiness | Controls when the container is ready to receive traffic. The platform polls this endpoint and only routes requests once it responds successfully. |
| スタートアップ | Checks whether the container has finished starting up. Liveness checks are paused until this passes—useful for containers with slow startup times like large model loads. |

On the Probes table, click Edit to configure the probe Path, Port, Initial delay (s), Timeout (s), Period (s), and Failure threshold.

### View the service artifact info

The Info tab displays the artifact's description, Artifact type, Created by information, Last modified date, Artifact repository ID, and Artifact ID. For a draft artifact, click next to the description to update it.

### View the Workload and endpoint

The Workload tab displays the Workload and endpoint associated with the artifact. Click View detailed info in Console to open the Workload in Console in a new tab.