)]}'
{"jenkins/jobs/packaging-mirror.yaml":[{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"aa418593613ff6795a8a803f24d626287f1833bc","unresolved":false,"context_lines":[{"line_number":58,"context_line":"      - net-info"},{"line_number":59,"context_line":"      - reprepro-import:"},{"line_number":60,"context_line":"          codename: \"{codename}\""},{"line_number":61,"context_line":"          reprepro: \"{reprepro}\""},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"    publishers:"},{"line_number":64,"context_line":"      - console-log"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"1aa78d24_64adf09a","line":61,"updated":"2016-07-11 18:11:35.000000000","message":"Just trying to think about this from a job expansion perspective. Does it make sense to have a single job to handle all the imports for each project/package? Then instead of having a job per codename you just have a single job for each project/package and pass in a list of codenames?\n\nMight be a little harder to get right in JJB but simplify things further down the line.","commit_id":"bd1c4bc2c153ea56673b1b7c3832f3146f839ea7"}]}
