{"push_id":1430019934,"size":1,"distinct_size":1,"ref":"refs/heads/paper-over-service-outage","head":"36fc1398c90c90c41342d120786a15ea5a25b077","before":"b6296db793f78c60e7a97cdbcbfc2dbe2de208cb","commits":[{"sha":"36fc1398c90c90c41342d120786a15ea5a25b077","author":{"name":"Michael Bridgen","email":"51def41f3b867ba43c7f77708ded5b71ff83e30b@squaremobius.net"},"message":"Make fluxsvc regrade async, gracefully stop\n\nWhen upgrading fluxsvc itself, we effectively ask Kubernetes to\nrestart the pod(s) that's watching the regrade process, and thereby\nlose the result.\n\nThis commit makes `fluxsvc` a special case which is run\nasynchronously. That is, the regrade is started but the service does\nnot wait for it to complete before reporting back to the user.\n\nThere is still a race between reporting back to the user, and the pod\nbeing restarted. For that reason, the service attempts to shut down\ngracefully, waiting until all release processes are completed, with a\ngenerous timeout. This means the release procedure has a chance to\nrecord what happened.","distinct":true,"url":"https://api.github.com/repos/weaveworks/flux/commits/36fc1398c90c90c41342d120786a15ea5a25b077"}]}
{"actor":{"display_login":"squaremo"}}