{"push_id":1203176812,"size":1,"distinct_size":1,"ref":"refs/heads/fail_early","head":"2470178ceb98c974fc13ac8fcea59398f2f013cf","before":"5750672de9c303e39f105933dd161a8ed91c3c4e","commits":[{"sha":"2470178ceb98c974fc13ac8fcea59398f2f013cf","author":{"name":"Hugh Saunders","email":"47286cbdd06d3507df2164ed11246f05cbe1c866@wherenow.org"},"message":"Fix subshell interaction with -e\n\nWhen -e is set, bash will:\n\"Exit immediately if a simple command exits with a non-zero status,\nunless the subshell is part of the command list immediately following a\n`while' or `until' keyword, part of the test in an `if' statement, part\nof the right-hand-side of a `&&' or `||' list, or if the command's\nreturn status is being inverted using `!'\"\n\nSo using -e in a subshell is not reliable especially if the subshell is\npart of larger logically combined statement.\n\nThis patch removes the reliance on -e in the subshell statements by\nreplacing ; with &&.\n\nThis patch also sets pipefail to catch errors that may have been masked\nby pipes.","distinct":true,"url":"https://api.github.com/repos/hughsaunders/jenkins-rpc/commits/2470178ceb98c974fc13ac8fcea59398f2f013cf"}]}
{"actor":{"display_login":"hughsaunders"}}