Draft
Conversation
Create a dedicated CI category/job for the travel planner stack and add end-to-end sanity checks, including optional live OVMS and travel_router query validation for scheduled/manual runs.
Co-authored-by: Cursor <cursoragent@cursor.com>
ezelanza
force-pushed
the
CI_for_agentic_kit
branch
from
a595cea to
a4a416b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this workflow does (short):
Set up – Check out repo, set up OS and Python (3.11 and 3.13 in parallel).
OVMS – Start LLM + VLM in Docker, then check they respond.
MCP – Start MCP servers, then check their ports.
Agents – Start travel planner agents, then check they answer a simple query (with retries and long timeout).
Overall – PLACEHOLDER
Cleanup – Always stop agents, MCP, and OVMS (even if something failed).