{"push_id":1557544445,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"9b2612afad818f8255d854191dda3ca0856d36cc","before":"bb18dbe84c6363465b97b35534e4c5d6ad572a1b","commits":[{"sha":"20c74ea6a545e3817903a086f290bb19fd457e64","author":{"name":"Gregory Haskins","email":"966aa87cce50a16f347ffab14449c22345f0d89d@gmail.com"},"message":"Use buildenv image for linter/protos\n\nAt one point in time, \"testenv\" was used for basic build-time\nprocesses such as linter, protos, and unit-tests.  Overtime, the\nrequirements for unit-testing grew and more dependencies were added.\nThis had the side-effect of requiring all prerequisites for unit-testing\nbe met for the other uses such as \"make protos\".  This led to a\nchicken-egg scenario when certain dependencies required the protos\nto be updated before they could be built, but the proto compilation\nrequired them to be built before it could run.\n\nThis is clearly not correct.\n\nWe fix this by making the image contruction more fine-grained.  We split\nthe basic functionality of \"testenv\" out into \"buildenv\".  We then\nallow the linter/protos process and the testenv image to consume buildenv.\n\nChange-Id: I5db05bac649c2fefe73b19ec06e44efe3d2b42fa\nSigned-off-by: Gregory Haskins <gregory.haskins@gmail.com>","distinct":true,"url":"https://api.github.com/repos/hyperledger/fabric/commits/20c74ea6a545e3817903a086f290bb19fd457e64"},{"sha":"9b2612afad818f8255d854191dda3ca0856d36cc","author":{"name":"Binh Nguyen","email":"9fe0bfc5b8eabcb37cf79b8ca753fe8084c608bb@us.ibm.com"},"message":"Merge \"Use buildenv image for linter/protos\"","distinct":true,"url":"https://api.github.com/repos/hyperledger/fabric/commits/9b2612afad818f8255d854191dda3ca0856d36cc"}]}
{"actor":{"display_login":"rjones-lf"}}