Skip to content

Conversation

@owtaylor
Copy link
Contributor

This PR adds a brew_builds parameter to the submit_request tool. I'm not too happy with it - I feel that more of the flexibility of the artifacts parameter in the API is needed - but I don't know exactly what part of that flexibility will be needed.

Is it better to to just have a artifacts parameter that literally matches the API and takes a list of:

class Artifact(TypedDict):
   id: str
   type: ArtifactType
   packages: NotRequired[list[str]]
   install: NotRequired[boolean]
   order: NotRequired[int]

?

owtaylor added 2 commits June 30, 2025 14:31
They were out-of-sync with the actual API

Assisted-by: claude-4-sonnet
- Modified server.py to accept and process `brew_builds`,
  allowing users to specify Brew builds as task IDs or NVR strings.
@thrix
Copy link
Collaborator

thrix commented Nov 12, 2025

@owtaylor sorry was busy with some other things, will check what we could do here

@owtaylor
Copy link
Contributor Author

@owtaylor sorry was busy with some other things, will check what we could do here

This isn't anything that we're using currently - with Project Jötnar, the main use of testing farm at the moment goes through the API rather than any sort of MCP. So use it as feedback if it's useful, otherwise feel free to close.

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.

2 participants