Register an image as an artifact
An artifact is a record of an image that already exists in your registry: a version label, the full image reference with a sha256 digest, and an optional note. Register one under 制品库 (Artifacts) with 登记制品 (Register artifact), and it becomes available for releases.
Registration does not build, upload or pull anything, and it does not check that the digest exists in the registry. The cluster pulls the image when you release it.

Steps
- In Infra, select the environment and application.
- Open 制品库 and click 登记制品.
- Fill in the dialog:
- 版本 (Version): a label such as
1.4.3. - 镜像地址 (Image address): the full reference including the digest, for example
registry.lan:5000/svc-user@sha256:followed by 64 lowercase hex characters. - 来源 / 更新说明 (Source / notes): a commit message, build number or other note.
- 版本 (Version): a label such as
- Save. The artifact appears in the list with its version, digest and source; artifacts without a source show 手动登记 (Registered manually).
Why digests only
The image reference must end in @sha256:<64 hex characters>. Tags, including latest, are rejected (“镜像必须包含完整的 sha256 摘要,不能使用 latest”). A digest identifies exactly one image, so a release record and a later rollback refer to precisely what ran. The guide to immutable digests explains how to get the digest from docker buildx or your registry.
Where artifacts are stored
Each artifact is one file, artifacts/<uuid>.yaml, in the project directory. It holds the ID, application, version, image, source and creation time. The image layers stay in your registry, which can be self-hosted on your machine or LAN as long as the cluster nodes can reach it. No cloud account is required.
Artifacts from AI builds
When an AI agent or script reports a successful build with devopspadctl runs record, the build becomes an artifact automatically, with the same ID as the run. Those entries link back to the build record via 查看构建记录 (View build record). See AI run records.
Frequently asked questions
Why does DevOpsPad reject image tags like latest?
A tag can point to different images over time, so a release record would not say what actually ran. Artifacts must use a full sha256 digest, which never changes.
Does registering an artifact upload my image?
No. Registration only stores the image address, version and notes in a small YAML file. The image itself stays in your OCI registry.