{"push_id":1164324590,"size":1,"distinct_size":1,"ref":"refs/heads/dynamically_determine_released_migrations","head":"d7ee977be437edd465c10a4193a8b8ade4dd953d","before":"97db648b5d1f5c7da977328aff9fd90955933d07","commits":[{"sha":"d7ee977be437edd465c10a4193a8b8ade4dd953d","author":{"name":"Nick Carboni","email":"f0d1c1e7979d14731de6bbea96d56f5bbce22da5@redhat.com"},"message":"Determine the released migrations when we run the test\n\nCommit 392423a created a spec which would fail if a migration\nin the current source tree was at an earlier timestamp than one\nthat has already been released, leaving us open to an issue where\nwe could run migrations out of order potentially causing schema\ninconsistencies across regions.\n\nThe previous method relied on a file to determine which migrations\nhad been released. When that file was not updated when new\nmigrations were backported we left ourselves open to a false positive.\n\nThis change pulls the migrations from the github api right before\nrunning the spec, ensuring that we have the latest data on backported\nmigrations.","distinct":true,"url":"https://api.github.com/repos/carbonin/manageiq/commits/d7ee977be437edd465c10a4193a8b8ade4dd953d"}]}
{"actor":{"display_login":"carbonin"}}