发布时构建并推送镜像
在您标记发布版本时自动构建容器
发布时构建并推送镜像 是 CoddyKit 上的免费 MLOps Academy 课时。 这是第 4 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 MLOps Academy 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 MLOps Academy 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
Build Only on Release
You do not ship an image on every commit. The release step builds and publishes a container only when you mark a version as ready. 📦
Trigger on a Tag
A common pattern fires the build when you push a git tag like v1.2.0, so a deliberate version, not a casual push, starts the deploy.
on:
push:
tags: ["v*"]What a Build Produces
The build packs your model API, its code, and dependencies into one image: a frozen, runnable snapshot that behaves the same on any machine.
A Registry Stores Images
A container registry like GHCR, ECR, or Docker Hub is where built images live so any server can later pull and run them.
Log In With a Secret
Before pushing, the workflow logs into the registry using a stored secret, never a hardcoded password, keeping credentials out of your code.
- uses: docker/login-action@v3
with:
password: ${{ secrets.REGISTRY_TOKEN }}Tag the Image Well
Give the image a clear tag that matches your release version. Reusing latest alone makes it impossible to tell which build is running.
myorg/model-api:v1.2.0Build and Push in One Action
The official Docker build-push action builds your Dockerfile and uploads the result to the registry in a single step.
- uses: docker/build-push-action@v6
with:
push: true
tags: myorg/model-api:v1.2.0Pin the Version, Not latest
Deploying a pinned tag like v1.2.0 means you always know exactly which model and code are live, and you can roll back to an earlier tag fast.
Cache Layers for Speed
Image builds reuse unchanged layers from a cache, so only the parts you actually changed rebuild. This keeps release builds quick.
Deploy Pulls the Image
Once pushed, your runtime simply pulls the tagged image and starts it. The same artifact you tested is the one that goes live, byte for byte.
docker pull myorg/model-api:v1.2.0Release Notes Close the Loop
Tie the image tag to a GitHub release with notes on what changed. Now anyone can trace a running container back to its exact code and model.
Quick Check
Why tag the released image with a version instead of only latest?
Recap
On a version tag, log in with a secret, build the image, and push it to a registry under a pinned tag. Your runtime pulls that exact artifact to go live.
常见问题解答
「发布时构建并推送镜像」课时是免费的吗？
是的 — 「发布时构建并推送镜像」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 MLOps Academy 课程的其余内容，请升级到 CoddyKit PRO。 MLOps Academy 课程共包含 4 节课。
「发布时构建并推送镜像」这节课中我会学到什么？
在您标记发布版本时自动构建容器 你通过在浏览器中直接运行的动手代码来练习 MLOps Academy，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 MLOps Academy 需要有经验吗？
无需任何先前经验。CoddyKit 上的 MLOps Academy 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 4 节课，共 4 节。
「发布时构建并推送镜像」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 MLOps Academy 课中编写并运行代码吗？
能。每节 MLOps Academy 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。