#792 feat: make flyte build the supported CI image build path Pull request opened by jeevb Summary • Add

tag: Optional[str] = None

to

Image.clone()

,

from_dockerfile()

,

from_debian_base()

, and

from_uv_script()

— enables CI workflows to inject a version tag (e.g.

$COMMIT_SHA

) at the same site where

registry

and

name

are set • Thread

force: bool = False

through

build_images

→

_build_images

→

_build_image_bg

→

build.aio

so the existing

ImageBuildEngine.build(force=)

param is reachable from the public API • Add

--force

flag to

flyte build

CLI via

BuildArguments

, wired into

BuildEnvCommand.invoke

• Deprecate

examples/image/ci_build_image.py

with a comment pointing to `flyte build`; add

_tag

coupling notes to

maint_tools/

Closes UN-12. Test Plan •

uv run pytest tests/flyte/test_image.py tests/flyte/test_deploy.py tests/cli/test_build.py -v

— 70 tests, all pass •

uv run flyte build --help

—

--force

appears in output • Pattern A (retag+rebuild):

Image.from_base(...).clone(registry=..., name=..., tag=os.environ.get("VERSION"))

+

flyte build images.py my_env --force

• Pattern B (Dockerfile):

Image.from_dockerfile(..., tag=os.environ.get("VERSION"))

+

flyte build images.py my_env --force

flyteorg/flyte-sdk