{"push_id":2092418064,"size":1,"distinct_size":1,"ref":"refs/heads/build_custom_pg_at_push_builds","head":"3cf1ef06c0044fbe3111972cf440d2ab320786f1","before":"9a714821a2cff9506ebc4ef01d082f24cee6cf63","commits":[{"sha":"3cf1ef06c0044fbe3111972cf440d2ab320786f1","author":{"name":"Burak Yucesoy","email":"1925213e59576ae3d962cd3de25faae6d21aeff2@citusdata.com"},"message":"Use custom compiled PostgreSQL on push builds\n\nPreviously we compiled PostgreSQL for PR and we used already compiled\nPostgreSQL packages for push builds. Compiling PostgreSQL allows us to\nrun isolation/vanilla tests. Thus we only ran those tests for PR builds.\nWe did not used compiled PostgreSQL for both builds because;\n- We wanted to run our tests against packages\n- Compiling takes too much time.\n\nHowever, there are some benefits in using custom compiled PostgreSQL\nin push builds instead of PR builds such as;\n- At the moment, we do not run isolation/vanilla tests until we open a\nPR, which does not make any sense.\n- After merging a PR (i.e. after push to the master) push builds run\nand we do not run isolation tests.\n- While merging community to enterprise, we have to open a temporary\nPR to make travis run isolation/vanilla tests.\n- With this change master branch will have its own cache that means\nevery branch originated from master branch can re-use master branch's\ncache. (Currently we cannot use cache for the first PR build)\n\nWith this PR we switch from using custom compiled for PR builds to push\nbuilds.","distinct":true,"url":"https://api.github.com/repos/citusdata/citus/commits/3cf1ef06c0044fbe3111972cf440d2ab320786f1"}]}
{"actor":{"display_login":"byucesoy"}}