I had the idea to somehow mark a commit as the last known good build for each targets which we have Travis-CI enabled. Basically the Travis-Ci script would mark the repository only if the build completed with no errors.
Same idea could be used to mark the last commit for which all automated tests were successfully run. Both of these would allow to track down exact PRs that broke something and then let one analyze how that one specific change in next commit can be fixed. I inquired the git mailing list (g...@vger.kernel.org) and they suggested using a git tag. The tag could encode any other information such as the OS/compiler version used to do the build with. This would also help when selecting to make a new master, since the maker could be aware for which OSs this master would compile/run out of the box without a problem. I believe this to be worth pursuing. Let me know what you think.
_______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
