{"push_id":1335378364,"size":1,"distinct_size":1,"ref":"refs/heads/feature/integration-testing","head":"e7b017832265e810821f98c03530ebd92f16aac0","before":"26377925e476bd88c2070a5092e37a3425aad91c","commits":[{"sha":"e7b017832265e810821f98c03530ebd92f16aac0","author":{"name":"Sam Hatfield","email":"bd13f473f6cea43255ec8534f4c807ac1f6b4523@gmail.com"},"message":"Add quick and full integration test targets\n\nThis commit adds integration test code in two phases:\n\n- quick-integration.hcl, for CI builds. Run with `make integration`\n- full-integration.sh, for nightly builds. This is triggered by setting\n  CVG_FULL_INTEGRATION in the environment\n\nWe are using docker for testing the same HCL file\nagainst multiple linux OSes. We need vagrant because we need\nan environment to test LVM modules, and it's a test of our plugin.\n\nTODOs:\n\n- Port blackbox tests to integration tests where appropriate\n- Set up nightly build machine, and add integration test to wercker\n- Right now, the docker target creates containers serially. I would like\n  to add a target where we simulate a cluster with containers. Should we\n  use docker compose for that? an HCL file? what?","distinct":true,"url":"https://api.github.com/repos/asteris-llc/converge/commits/e7b017832265e810821f98c03530ebd92f16aac0"}]}
{"actor":{"display_login":"sehqlr"}}