Skip to content

ci: install flytectl directly instead of the broken setup action#3449

Closed
1fanwang wants to merge 1 commit into
flyteorg:masterfrom
1fanwang:fix-ci-flytectl-install
Closed

ci: install flytectl directly instead of the broken setup action#3449
1fanwang wants to merge 1 commit into
flyteorg:masterfrom
1fanwang:fix-ci-flytectl-install

Conversation

@1fanwang

Copy link
Copy Markdown
Contributor

Why are the changes needed?

The integration jobs are red on master and on every PR. They fail at the Install FlyteCTL step:

##[error]Cannot read properties of undefined (reading 'assets')

unionai-oss/flytectl-setup-action@master resolves "latest" by listing the first page of flyteorg/flyte releases, filtering to flytectl/-prefixed tags, and reading i[0].assets. That page is now entirely Flyte 2.0 (v2.0.x) release tags — no flytectl/ release appears on it — so the filtered list is empty and i[0].assets throws. (The ctl.flyte.org install script has the same first-page limitation, so it isn't a workaround either.)

What changes were proposed in this pull request?

Install flytectl by downloading the last published release, flytectl/v0.9.8, directly from its asset URL — no release-list resolution involved. v0.9.8 is the same version the action installed back when it worked.

Unblocks the red integration checks across all open PRs.

How was this patch tested?

CI on this PR is the real check — the integration jobs now get past the FlyteCTL install and into flytectl demo start. Out of band I confirmed the asset URL resolves and the tarball holds the flytectl binary at its root. I can't run GitHub Actions locally, so I'm relying on this PR's run for the green.

Check all the applicable boxes

  • I updated the documentation accordingly.
  • All new and existing tests passed.
  • All commits are signed-off.

unionai-oss/flytectl-setup-action resolves the latest flytectl from the
first page of flyteorg/flyte releases. That page is now entirely Flyte 2.0
(v2.0.x) tags with no flytectl/ release, so the action crashes with
"Cannot read properties of undefined (reading 'assets')" and reds the
integration jobs on master and every PR. Download the last flytectl
release (v0.9.8) from its asset URL instead.

Signed-off-by: 1fanwang <1fannnw@gmail.com>
@1fanwang

Copy link
Copy Markdown
Contributor Author

Folded into #3448 — the flytectl install fix and the plugin-deps fix have to ship on the same branch to go green (each PR was red only on the other's failure).

@1fanwang 1fanwang closed this Jun 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant