<#7268 ci: add devbox integration test running hel...
# flyte-github
a
#7268 ci: add devbox integration test running hello world via flyte CLI Pull request opened by pingsutw Why are the changes needed? We don't currently exercise the devbox image end-to-end in CI. A PR can successfully build the devbox bundled image yet still produce a cluster that can't actually execute a task. This adds a smoke test that boots the freshly built devbox and runs a hello-world task against it. What changes were proposed in this pull request? Adds an
integration-test
job to `.github/workflows/flyte-binary-v2.yml`: • Reuses the
single-binary-image
artifact from
build-and-push-single-binary-image
(no flyte-binary rebuild). • Builds the devbox image for the current branch (
linux/amd64
,
--load
as
flyte-devbox:latest
), pulling from the existing
demo-cpu
GHA buildx cache. • Boots the cluster with
make -C docker/devbox-bundled start
and waits for the flyte endpoint on
:30080
. • Installs the
flyte
SDK, writes a minimal hello-world task + a config pointing at
dns:///localhost:30080
with
insecure: true
, and runs
flyte --config config.yaml run hello.py main --numbers '[1,2,3]'
.
flyte run
blocks on the remote run and exits non-zero on failure, so the job fails automatically if the task doesn't succeed. • Dumps
docker logs flyte-devbox
on failure and always stops the container. Labels added How was this patch tested? Will be validated by CI on this PR. Check all the applicable boxes • I updated the documentation accordingly. • All new and existing tests passed. • All commits are signed-off. •
main
• #6583 • ci: add devbox integration test running hello world via flyte CLI 👈 flyteorg/flyte