fix(models): correct Build and Buildset to match Zuul API response fo…#10
Merged
clappingmonkey merged 1 commit intomainfrom Mar 17, 2026
Merged
fix(models): correct Build and Buildset to match Zuul API response fo…#10clappingmonkey merged 1 commit intomainfrom
clappingmonkey merged 1 commit intomainfrom
Conversation
…rmat The Zuul API returns ref information as nested objects, not as root-level fields. This change fixes the data models to correctly parse the API responses: - Add new Ref struct for nested ref objects containing project, branch, change, patchset, ref, oldrev, newrev, and ref_url fields - Update Build struct: change Ref from string to *Ref object, remove root-level project/branch/change/patchset/ref_url fields, add execute_time, held, error_detail, final, event_timestamp, and queue_item_uuid fields, rename node_name to nodeset - Update Buildset struct: replace root-level ref fields with Refs []Ref array, add event_timestamp and queue_item_uuid fields Tested against OpenDev Zuul (zuul.opendev.org) and verified that get_build, list_builds, and list_buildsets correctly parse and serialize the new nested ref structure.
clappingmonkey
pushed a commit
that referenced
this pull request
Mar 17, 2026
🤖 I have created a release *beep* *boop* --- ## [0.2.2](v0.2.1...v0.2.2) (2026-03-17) ### Bug Fixes * **models:** correct Build and Buildset to match Zuul API response fo… ([#10](#10)) ([232efe0](232efe0)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: zuul-mcp-bot[bot] <268975808+zuul-mcp-bot[bot]@users.noreply.github.com>
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.
…rmat
The Zuul API returns ref information as nested objects, not as root-level fields. This change fixes the data models to correctly parse the API responses:
Tested against OpenDev Zuul (zuul.opendev.org) and verified that get_build, list_builds, and list_buildsets correctly parse and serialize the new nested ref structure.