Skip to content

ci(evals): run evals on the flyte-agent-plugins-evals project - #30

Open
cosmicBboy wants to merge 1 commit into
mainfrom
ci/evals-project
Open

ci(evals): run evals on the flyte-agent-plugins-evals project#30
cosmicBboy wants to merge 1 commit into
mainfrom
ci/evals-project

Conversation

@cosmicBboy

Copy link
Copy Markdown
Collaborator

What

Point the demo.hosted eval runs at the dedicated flyte-agent-plugins-evals project instead of the shared flytesnacks project.

  • evals/config/flyte.yamltask.project: flyte-agent-plugins-evals. The CI driver (run_ci.py) reads task.project from this config, so this switches both the GitHub Actions flyte-evals job and local python -m evals.workflows.run_ci runs.
  • Updated the eval_wf.py module docstring to match.

Org (demo) and domain (development) are unchanged; only the project moves.

Validation

Verified end-to-end on CI before this PR (on the fix/kind-smoke-deps branch, commit 01b625b): the flyte-evals job ran and succeeded against flyte-agent-plugins-evals, confirming the project exists on demo.hosted and the glm-api-key secret is reachable there.

🤖 Generated with Claude Code

…cks)

Point the demo.hosted eval runs at the dedicated flyte-agent-plugins-evals
project instead of the shared flytesnacks project. The driver reads
task.project from evals/config/flyte.yaml, so this switches both the flyte-evals
CI job and local runs.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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