)]}'
{"jenkins/jobs/tripleo.yaml":[{"author":{"_account_id":360,"name":"Dan Prince","email":"dprince@redhat.com","username":"dan-prince"},"change_message_id":"d2235d4e0894c3a102b8fad3b3dba614de74e257","unresolved":false,"context_lines":[{"line_number":148,"context_line":"          export DIB_COMMON_ELEMENTS\u003d\"common-venv stackuser pypi-openstack\""},{"line_number":149,"context_line":"          export TRIPLEO_TEST\u003dovercloud"},{"line_number":150,"context_line":"          export USE_IRONIC\u003d1"},{"line_number":151,"context_line":"          export USE_MERGEPY\u003d0"},{"line_number":152,"context_line":"          sudo chown -hR $(whoami) /opt/git"},{"line_number":153,"context_line":"          export OVERCLOUD_CONTROLSCALE\u003d1"},{"line_number":154,"context_line":"          export USE_CIRROS\u003d1"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"3a961159_44543254","line":151,"updated":"2014-12-08 17:20:33.000000000","message":"Also, see b8b2035405898797d4a11d01daac759f22e0a784 in tripleo-ci where we are starting to prefer setting control variables within the tripleo-ci project itself. This allows us to more easily test config changes to CI itself (whereas previously we\u0027d have to wait for the infra change to land before we knew if it worked).","commit_id":"7caed7adbc768b9dce38689a3e4b27852ad99c3a"}]}
