Re: [PATCH v1 2/2] travis-ci: disable GIT_TEST_HTTPD for macOS

From: Jeff King <peff@peff.net>
Date: Nov 11, 2016, 09:28 UTC
Message-ID: <20161111092824.qqgrmhtkuw3wpbwa@sigill.intra.peff.net>
In-Reply-To: <BAB2E4AE-7241-4991-A993-A60DBA75092B@gmail.com>

On Fri, Nov 11, 2016 at 10:13:44AM +0100, Lars Schneider wrote:

Show 16 quoted lines

> > If you did want to have a more real-world network-based test, I think
> > the right solution is not for GitHub to set up a bunch of mock servers,
> > but to design client-side tests that hit the _real_ GitHub (or GitLab,
> > or whatever) and perform some basic operations. OTOH, people running
> > "master" (or "next", etc) are doing that implicitly every day.
> 
> That is actually a neat idea. We could setup a test repo on each of the major 
> Git hosting sites and then the TravisCI run could clone a repo and push
> changes to it. That shouldn't take long and would probably be a good real
> world test.
> 
> The credentials of these repos could be stored encrypted in Travis CI [1].
> 
> Where would such a test repo live on github.com? On github.com/git or would
> you prefer a separate organization? (no worries, I am not going to tackle this
> anytime soon -- too many things in my backlog already).

I think I'd prefer for it to live outside of the "git" organization entirely, if only because it's credentials will be necessarily less secure. It would be nice if people could point the suite at their own user/repo, too, so they can run it outside of travis.

> BTW: I just noticed https://github.com/git/hello-world ... is this legitimate
> or did someone hack github.com/git? :)

Hmm. I wondered myself. There's no audit record of who created it, but the creation timestamp is from 2008-07-23, which predates a lot of the logging. So offhand, I'd say the likely explanation is "Scott Chacon experimenting".

It's probably worth cleaning out now, though.

-Peff