On 20/05/15 14:37, Howard Pritchard wrote: > It would also be easy to trap the I-want-to-bypass-PR-because-I > know-what-I'm-doing-developer with a second level of protection. Just > set up a jenkins project that does a smoke test after ever commit to > master. If the smoke test fails, send a naughty-gram to the committer > and copy devel. Pretty soon the developer will get trained to use the PR > process, unless they are that engineer I've yet to meet who always > writes flawless code.
VMware used to have a bot that tweeted info about their testing, including "$USER just broke the build at VMWare"; for example: https://twitter.com/vmwarepbs/status/4634524702 :-) -- Christopher Samuel Senior Systems Administrator VLSCI - Victorian Life Sciences Computation Initiative Email: sam...@unimelb.edu.au Phone: +61 (0)3 903 55545 http://www.vlsci.org.au/ http://twitter.com/vlsci
