)]}'
{"jenkins/jobs/devstack-gate.yaml":[{"author":{"_account_id":7118,"name":"Ian Wienand","email":"iwienand@redhat.com","username":"iwienand"},"change_message_id":"da67c20d75c94d4a4349cfbb7856a2d2dd2c0775","unresolved":false,"context_lines":[{"line_number":2349,"context_line":"          if [ \"$BRANCH_OVERRIDE\" !\u003d \"default\" ] ; then"},{"line_number":2350,"context_line":"              export OVERRIDE_ZUUL_BRANCH\u003d$BRANCH_OVERRIDE"},{"line_number":2351,"context_line":"          fi"},{"line_number":2352,"context_line":"          export TARGET_RUN_SMOKE\u003dtrue"},{"line_number":2353,"context_line":"          export GRENADE_PLUGINRC+\u003d$\u0027\\n\u0027\"enable_grenade_plugin ironic https://git.openstack.org/openstack/ironic\""},{"line_number":2354,"context_line":"          export GRENADE_PLUGINRC+\u003d$\u0027\\n\u0027\"enable_grenade_plugin ironic-inspector https://git.openstack.org/openstack/ironic-inspector\""},{"line_number":2355,"context_line":"          cp devstack-gate/devstack-vm-gate-wrap.sh ./safe-devstack-vm-gate-wrap.sh"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1aa78d24_3bd055f7","line":2352,"updated":"2016-07-15 04:16:38.000000000","message":"I don\u0027t get it ... Ieb5498a69aec7b8c2d2b48e2ae89ad97a086e87e seemed to set this to false in devstack-gate and that patch seemed to confuse better minds than me...\n\nwas this disabled by mistake there?  are tests expected to enable this by hand now? \n\ni\u0027d like to see clarity around this before we move on","commit_id":"bca95d0b926db6e1b7f6267be8c1e0c205367473"},{"author":{"_account_id":18653,"name":"Milan Kováčik","email":"mkovacik@redhat.com","username":"dparalen"},"change_message_id":"59220fca28d4ac1891eafe0c86afb9a707a6ba80","unresolved":false,"context_lines":[{"line_number":2349,"context_line":"          if [ \"$BRANCH_OVERRIDE\" !\u003d \"default\" ] ; then"},{"line_number":2350,"context_line":"              export OVERRIDE_ZUUL_BRANCH\u003d$BRANCH_OVERRIDE"},{"line_number":2351,"context_line":"          fi"},{"line_number":2352,"context_line":"          export TARGET_RUN_SMOKE\u003dtrue"},{"line_number":2353,"context_line":"          export GRENADE_PLUGINRC+\u003d$\u0027\\n\u0027\"enable_grenade_plugin ironic https://git.openstack.org/openstack/ironic\""},{"line_number":2354,"context_line":"          export GRENADE_PLUGINRC+\u003d$\u0027\\n\u0027\"enable_grenade_plugin ironic-inspector https://git.openstack.org/openstack/ironic-inspector\""},{"line_number":2355,"context_line":"          cp devstack-gate/devstack-vm-gate-wrap.sh ./safe-devstack-vm-gate-wrap.sh"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"1aa78d24_6f0217b6","line":2352,"in_reply_to":"1aa78d24_3bd055f7","updated":"2016-07-15 06:51:04.000000000","message":"Ian, this is how I understand it(please, correct me if I\u0027m wrong): the goal of grenade is smoke test the base, create some resources (such as a server or a network) that should survive the upgrade, do the upgrade and verify that the resources are still functional[1][2]. Some auxiliary services (including Inspector) might not create any resources, so to verify those services were not broken by the upgrade one has to re-run (smoke) tests at least in their respective gate jobs. \n\n[1] https://github.com/openstack-dev/grenade/blob/master/README.rst#theory-of-upgrade\n[2] https://github.com/openstack-dev/grenade/blob/master/README.rst#basic-flow","commit_id":"bca95d0b926db6e1b7f6267be8c1e0c205367473"}]}
