)]}'
{"releasenotes/notes/mqtt-report-build-page-1780225ca98c7456.yaml":[{"author":{"_account_id":9311,"name":"Tristan Cacqueray","email":"tdecacqu@redhat.com","username":"tristanC"},"change_message_id":"f38d63d4cca6da5b8de359bd1576b916323405ed","unresolved":false,"context_lines":[{"line_number":5,"context_line":"    log_url, this was only true as long as :attr:`tenant.report-build-page` was"},{"line_number":6,"context_line":"    disabled. As soon as the setting was enabled, the MQTT reporter reported the"},{"line_number":7,"context_line":"    url to the build\u0027s result page in Zuul. As MQTT is meant to be consumed by"},{"line_number":8,"context_line":"    machines, this broke use cases like log post processing."},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"    This was fixed so that the :attr:`\u003cmqtt schema\u003e.buildset.builds.log_url` now"},{"line_number":11,"context_line":"    always contains the log url, while an additional field"}],"source_content_type":"text/x-yaml","patch_set":6,"id":"bf51134e_0420b7ab","line":8,"updated":"2020-06-23 18:35:35.000000000","message":"Is the log_url really useful? Wouldn\u0027t it be better if only the build url was present in the mqtt event?","commit_id":"cfb83779449bd64ecb4b9e0f0747c3b3e6a26b36"},{"author":{"_account_id":27952,"name":"Felix Edel","email":"felix.edel@bmw.de","username":"felix.schmidt"},"change_message_id":"cd72bac01e72d6dec05e41ccf476d760fddfba44","unresolved":false,"context_lines":[{"line_number":5,"context_line":"    log_url, this was only true as long as :attr:`tenant.report-build-page` was"},{"line_number":6,"context_line":"    disabled. As soon as the setting was enabled, the MQTT reporter reported the"},{"line_number":7,"context_line":"    url to the build\u0027s result page in Zuul. As MQTT is meant to be consumed by"},{"line_number":8,"context_line":"    machines, this broke use cases like log post processing."},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"    This was fixed so that the :attr:`\u003cmqtt schema\u003e.buildset.builds.log_url` now"},{"line_number":11,"context_line":"    always contains the log url, while an additional field"}],"source_content_type":"text/x-yaml","patch_set":6,"id":"bf51134e_eadaa575","line":8,"in_reply_to":"bf51134e_0420b7ab","updated":"2020-06-24 06:00:52.000000000","message":"Yes, the log_url is very useful if you want to process/analyze the Ansible log (which we are doing). Having only an HTML page as result URL would break this use case unless we want to extract the log_url from the build\u0027s HTML page (which we don\u0027t).","commit_id":"cfb83779449bd64ecb4b9e0f0747c3b3e6a26b36"},{"author":{"_account_id":9311,"name":"Tristan Cacqueray","email":"tdecacqu@redhat.com","username":"tristanC"},"change_message_id":"e2e058809ad2715a1ece78df7bd9fa6eb2d3a03d","unresolved":false,"context_lines":[{"line_number":5,"context_line":"    log_url, this was only true as long as :attr:`tenant.report-build-page` was"},{"line_number":6,"context_line":"    disabled. As soon as the setting was enabled, the MQTT reporter reported the"},{"line_number":7,"context_line":"    url to the build\u0027s result page in Zuul. As MQTT is meant to be consumed by"},{"line_number":8,"context_line":"    machines, this broke use cases like log post processing."},{"line_number":9,"context_line":""},{"line_number":10,"context_line":"    This was fixed so that the :attr:`\u003cmqtt schema\u003e.buildset.builds.log_url` now"},{"line_number":11,"context_line":"    always contains the log url, while an additional field"}],"source_content_type":"text/x-yaml","patch_set":6,"id":"bf51134e_38ca706d","line":8,"in_reply_to":"bf51134e_eadaa575","updated":"2020-07-08 12:03:58.000000000","message":"I meant the build url api (which need to be computed from the html url). I remember using the log-url to be unreliable, for example when the zuul-info/inventory.yaml was not reachable, and I had to switch to the REST endpoint to get consistent build information.","commit_id":"cfb83779449bd64ecb4b9e0f0747c3b3e6a26b36"}]}