)]}'
{"playbooks/roles/gerrit/tasks/start.yaml":[{"author":{"_account_id":7118,"name":"Ian Wienand","email":"iwienand@redhat.com","username":"iwienand"},"change_message_id":"6a4a7c822541427e1524c350eeb0b779e8494ca6","unresolved":true,"context_lines":[{"line_number":6,"context_line":"    chdir: /etc/gerrit-compose/"},{"line_number":7,"context_line":"  when: gerrit_run_init | bool"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"- name: Run gerrit reindex"},{"line_number":10,"context_line":"  shell:"},{"line_number":11,"context_line":"    cmd: \u003e"},{"line_number":12,"context_line":"      docker-compose run shell"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"ba52ad43_6fa169e1","line":9,"updated":"2023-01-17 22:56:43.000000000","message":"It is probably over-engineering this ... but I wonder if this could be a variable that stamps when it was done.  For example, you\u0027d have something like\n\n # these versions require a reindex before starting when upgrading\n gerrit_upgrade_reindex:\n   - 3.6\n   - 3.X\n  \nand a task that first checks the gerrit version, and if it\u0027s in the upgrade_reindex list, then looks for \u0027/var/gerrit/stamp/{{ version }}.reindex.stamp\u0027, and if it\u0027s not there, runs the reindex and makes the stamp ...\n\nSeems like we could actually use that in the upgrade checklist too...","commit_id":"90440837a72b3dacfd108ca84d6764eccc4f520a"},{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"758c27ad41ef309dc9afe116baa6d88d3e093a3b","unresolved":true,"context_lines":[{"line_number":6,"context_line":"    chdir: /etc/gerrit-compose/"},{"line_number":7,"context_line":"  when: gerrit_run_init | bool"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"- name: Run gerrit reindex"},{"line_number":10,"context_line":"  shell:"},{"line_number":11,"context_line":"    cmd: \u003e"},{"line_number":12,"context_line":"      docker-compose run shell"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"97af14ac_e0573993","line":9,"in_reply_to":"ba52ad43_6fa169e1","updated":"2023-01-19 18:40:34.000000000","message":"I think this would be a good thing to implement if we wanted to fully automate the Gerrit installs. However, I think that is well beyond having a simple test for the upgrade?\n\nI worry that this will complicate something that is simple today with little benefit beyond the test if we don\u0027t get to the point of automated upgrades.\n\nThat said I think automated upgrades would be neat to implement, but maybe we can have this sort of tooling when we get there?","commit_id":"90440837a72b3dacfd108ca84d6764eccc4f520a"}]}