)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":5196,"name":"Matthew Treinish","email":"mtreinish@kortar.org","username":"treinish"},"change_message_id":"6fe98b0c2ef95e90745a487eba3b4ce1aaf0df36","unresolved":false,"context_lines":[{"line_number":7,"context_line":"add \u0027tempest\u0027 in puppet-openstack-integration jobs"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"To have the puppet integration jobs part of Health [1] project, we want"},{"line_number":10,"context_line":"logstash about to read subunit-files."},{"line_number":11,"context_line":"So we need to rename the jobs to match this job filter:"},{"line_number":12,"context_line":"job-filter: \u0027.*(tempest|grenade)-dsvm.*\u0027"},{"line_number":13,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"7a740942_7515e199","line":10,"updated":"2015-12-08 20:09:51.000000000","message":"So it\u0027s technically not logstash that\u0027s reading the subunit files. It\u0027s the logstash gearman client that processes events triggered by jenkins zmq plugin. This emits a gearman job for the subunit gearman worker to populate the subunit2sql db with the subunit file from the job. It\u0027s an overly complicated mechanism that I just tacked on the subunit processing to the side. :)\n\nFWIW, the whole mechanism behind this is documented here:\n\nhttp://docs.openstack.org/infra/system-config/logstash.html#system-architecture","commit_id":"bc458317ddd0b007f5c47931ea67f62d544ea238"}]}