git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Lars Schneider <larsxschneider@gmail.com>
Date
Nov 11, 2016, 09:13 UTC
Message-ID
<BAB2E4AE-7241-4991-A993-A60DBA75092B@gmail.com>
In-Reply-To
<20161111084725.jkdsdt4yslzsuh6d@sigill.intra.peff.net>
On 11 Nov 2016, at 09:47, Jeff King <peff@peff.net> wrote:
Show 20 quoted lines
> On Fri, Nov 11, 2016 at 09:22:51AM +0100, Lars Schneider wrote:
> 
>> There would be an alternative way to approach the problem:
>> Someone (GitHub?, BitBucket?, GitLab?, ...) could setup a bunch of webservers
>> with popular configurations and a way to reset a clean test environment. Then 
>> the TravisCI client tests could go against these servers.
>> 
>> I realize that this idea is probably unrealistic because too much setup and
>> maintenance work would be required.
> 
> Yeah, it seems like it adds a lot of complexity for little gain. Plus it
> creates a network dependency on running the tests. I know you care
> mostly about Travis, but I am much more interested in all of the people
> (developers and not) who run "make test" on their own platforms.
> 
> 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).

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

Cheers, Lars

[1] https://docs.travis-ci.com/user/environment-variables/#Defining-encrypted-variables-in-.travis.yml
Previous: Jeff KingNext: Jeff King
Message 24 of 35 in “Fix default macOS build locally and on Travis CI”
  1. 0/2 Fix default macOS build locally and on Travis CIlarsxschneider@gmail.com, Oct 17, 2016
  2. 1/2 config.mak.in: set NO_OPENSSL and APPLE_COMMON_CRYPTO for macOS >10.11larsxschneider@gmail.com, Oct 17, 2016
  3. Jeff KingOct 17, 2016
  4. Lars SchneiderNov 6, 2016
  5. Jeff KingNov 7, 2016
  6. Paul SmithNov 7, 2016
  7. Jeff KingNov 7, 2016
  8. Paul SmithNov 7, 2016
  9. Torsten BögershausenNov 9, 2016
  10. Lars SchneiderNov 9, 2016
  11. Torsten BögershausenNov 9, 2016
  12. Makefile: set NO_OPENSSL on macOS by defaultlarsxschneider@gmail.com, Nov 10, 2016
  13. 2/2 travis-ci: disable GIT_TEST_HTTPD for macOSlarsxschneider@gmail.com, Oct 17, 2016
  14. Lars SchneiderNov 6, 2016
  15. Jeff KingNov 7, 2016
  16. Lars SchneiderNov 10, 2016
  17. Jeff KingNov 10, 2016
  18. Junio C HamanoNov 10, 2016
  19. Jeff KingNov 10, 2016
  20. Junio C HamanoNov 10, 2016
  21. Jeff KingNov 10, 2016
  22. Lars SchneiderNov 11, 2016
  23. Jeff KingNov 11, 2016
  24. Lars SchneiderNov 11, 2016
  25. Jeff KingNov 11, 2016
  26. Heiko VoigtNov 15, 2016
  27. Lars SchneiderNov 15, 2016
  28. Jeff KingNov 15, 2016
  29. Heiko VoigtNov 16, 2016
  30. Torsten BögershausenNov 16, 2016
  31. Junio C HamanoNov 9, 2016
  32. Torsten BögershausenNov 10, 2016
  33. Lars SchneiderNov 10, 2016
  34. Junio C HamanoNov 10, 2016
  35. Lars SchneiderNov 11, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.