)]}'
{".zuul.yaml":[{"author":{"_account_id":2,"name":"Monty Taylor","email":"mordred@inaugust.com","username":"mordred"},"change_message_id":"30d5b781d333d5677c6e0157ef0dc255c00cff51","unresolved":true,"context_lines":[{"line_number":66,"context_line":"        - tox-py35:"},{"line_number":67,"context_line":"            nodeset: ubuntu-xenial"},{"line_number":68,"context_line":"        - build-python-release"},{"line_number":69,"context_line":"        - opendev-buildset-registry"},{"line_number":70,"context_line":"        - gear-build-opendev-image"},{"line_number":71,"context_line":"    gate:"},{"line_number":72,"context_line":"      jobs:"}],"source_content_type":"text/x-yaml","patch_set":6,"id":"07b04477_06fbbeb5","line":69,"updated":"2021-02-11 18:48:39.000000000","message":"I don\u0027t think you need this. The build job should run a registry as part of itself if there isn\u0027t a shared one. explicit buildset registry is only needed when there are more than one job that want to share it.","commit_id":"8fe2e8c645547489c87607dd6c5ffe1c970f067a"},{"author":{"_account_id":2,"name":"Monty Taylor","email":"mordred@inaugust.com","username":"mordred"},"change_message_id":"30d5b781d333d5677c6e0157ef0dc255c00cff51","unresolved":true,"context_lines":[{"line_number":75,"context_line":"        - tox-py35:"},{"line_number":76,"context_line":"            nodeset: ubuntu-xenial"},{"line_number":77,"context_line":"        - build-python-release"},{"line_number":78,"context_line":"        - opendev-buildset-registry"},{"line_number":79,"context_line":"        - gear-upload-opendev-image"},{"line_number":80,"context_line":"    promote:"},{"line_number":81,"context_line":"      jobs:"}],"source_content_type":"text/x-yaml","patch_set":6,"id":"cbd2342d_90c4312a","line":78,"updated":"2021-02-11 18:48:39.000000000","message":"Same.","commit_id":"8fe2e8c645547489c87607dd6c5ffe1c970f067a"}]}