{"push_id":1064746680,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"24daa741da0c3ce554477cbecdf7d3237a589ff1","before":"68c986db5205b9434986b08d3d3ddb655f35f106","commits":[{"sha":"16b7c693dee595017070985cd48bb41e0d1aa149","author":{"email":"2048b22ac0881f917af3e938105055ab85498548@suse.com","name":"Andreas Jaeger"},"message":"Rework slave-cleanup\n\nThe current approach does not work at all: Every job runs \"git clean\" as\npart of set up of workspace. So, the marker we use is deleted and all\nthe content as well.\n\nSo, what we can do is run the \"git clean\" also after a run, so that the\nworkspace is minimal between invocations and the initial \"git clean\"\nbecomes a nop. This helps with overall space on the proposal slave\nsince only the active job will use .tox directories etc. Since there's\nno regular cleanup of workspace, this also helps when jobs get retired,\nthe workspace will continue to exist - but with the cleanup done, it's\nmuch smaller.\n\nChange-Id: I8b17724905634aa2f7cc657de073ee7cfe10f781","distinct":true,"url":"https://api.github.com/repos/openstack-infra/project-config/commits/16b7c693dee595017070985cd48bb41e0d1aa149"},{"sha":"24daa741da0c3ce554477cbecdf7d3237a589ff1","author":{"email":"d95b56ce41a2e1ac4cecdd398defd7414407cc08@review.openstack.org","name":"Jenkins"},"message":"Merge \"Rework slave-cleanup\"","distinct":true,"url":"https://api.github.com/repos/openstack-infra/project-config/commits/24daa741da0c3ce554477cbecdf7d3237a589ff1"}]}