On 25 Sep 2015, at 10:05, Luke Diamand <l...@diamand.org> wrote: > On 25 September 2015 at 08:27, Johannes Schindelin > <johannes.schinde...@gmx.de> wrote: >> Hi, >> >> On 2015-09-25 05:14, Dennis Kaarsemaker wrote: >>> On do, 2015-09-24 at 17:41 -0700, Junio C Hamano wrote: >>>> larsxschnei...@gmail.com writes: >>>> >>>>> My idea is that the owner of "https://github.com/git/git"; enables this >>>>> account >>>>> for Travis (it's free!). Then we would automatically get the test state >>>>> for all >>>>> official branches. >>>> >>>> The last time I heard about this "it's free" thing, I thought I >>>> heard that it wants write access to the repository. >>> >>> It does not need write access to the git data, only to auxiliary GitHub >>> data: commit status and deployment status (where it can put "this >>> commit failed tests"), repository hooks (to set up build triggers), >>> team membership (ro) and email addresses (ro). >> >> If that still elicits concerns, a fork could be set up that is automatically >> kept up-to-date via a web hook, and enable Travis CI there. >> >> Junio, if that is something with which you feel more comfortable, I would be >> willing to set it up. Even if the visibility (read: impact) would be higher >> if the badges were attached to https://github.com/git/git proper... >> > > It would be less intrusive for the CI system to have a fork. Otherwise > other people using git with the same CI system will get annoying merge > conflicts, and we'll also end up with a repo littered with the control > files from past CI systems if the CI system is ever changed. > > From past experience, if it's configured to email people when things > break, sooner or later it will email the wrong people, probably once > every few seconds over a weekend. > > Automated testing is a Good Thing, but it's still software, so needs > maintenance or it will break.
I completely agree with your argument about emails and that software needs maintenance. We could setup this CI to not send any emails. We still could inspect the build/test state of each branch on the Travis CI website. I believe this is valuable because not everyone has e.g. a Mac system at hand to run all tests. This is no theoretical example because t9819 is broken on maint using a Mac. Lars-- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
