- 12 Oct, 2018 13 commits
-
-
(cherry picked from commit 24d17562)
Edward Thomson committed -
(cherry picked from commit 24b8dd82)
Edward Thomson committed -
(cherry picked from commit 465f8b51)
Edward Thomson committed -
(cherry picked from commit b00672b9)
Edward Thomson committed -
Simplify the names for the tests, removing the unnecessary "libgit2-clar" prefix. Make "all" the new default test run, and include the online tests by default (since HTTPS should always be enabled). For the CI tests, create an offline-only test, then the various online tests. (cherry picked from commit ce798b25)
Edward Thomson committed -
(cherry picked from commit 61eaaadf)
Etienne Samson committed -
(cherry picked from commit 149790b9)
Etienne Samson committed -
(cherry picked from commit 4c969618)
Etienne Samson committed -
(cherry picked from commit 0fb8c1d0)
Etienne Samson committed -
The goal is to let cmake manage the parallelism (cherry picked from commit 1f4ada2a)
Etienne Samson committed -
(cherry picked from commit 573c4089)
Etienne Samson committed -
(cherry picked from commit 74b0a432)
Etienne Samson committed -
(cherry picked from commit 2f4e7cb0)
Etienne Samson committed
-
- 03 Jan, 2018 3 commits
-
-
Some tests shall be run against our own SSH server we spin up in Travis. As those need to be run separate from our previous tests which run against git-daemon, we have to do this in a separate step. Instead of bundling all that knowledge in the CI script, move it into the test build instructions by creating a new test target.
Patrick Steinhardt committed -
Right now, we test our credential callback code twice, once via SSH on localhost and once via a non-existent GitHub repository. While the first URL makes sense to be configurable, it does not make sense to hard-code the non-existing repository, which requires us to call tests multiple times. Instead, we can just inline the URL into another set of tests.
Patrick Steinhardt committed -
We support two types of passing credentials to the proxy, either via the URL or explicitly by specifying user and password. We test these types by modifying the proxy URL and executing the tests twice, which is in fact unnecessary and requires us to maintain the list of environment variables and test executions across multiple CI infrastructures. To fix the situation, we can just always pass the host, port, user and password to the tests. The tests can then assemble the complete URL either with or without included credentials, allowing us to test both cases in-process.
Patrick Steinhardt committed
-
- 06 Nov, 2017 1 commit
-
-
By default, CMake will not build our examples directory. As we do not instruct either the MinGW or MSVC builds on AppVeyor to enable building these examples, we cannot verify that those examples at least build on Windows systems. Fix that by passing `-DBUILD_EXAMPLES=ON` to AppVeyor's CMake invocation.
Patrick Steinhardt committed
-
- 31 Oct, 2017 2 commits
-
-
Carlos Martín Nieto committed
-
The macOS tests are by far the slowest right now. This attempts to remedy the situation somewhat by asking clar to put its test data on a ramdisk.
Carlos Martín Nieto committed
-
- 06 Oct, 2017 1 commit
-
-
Move back to Travis's VM infrastructure for efficiency.
Edward Thomson committed
-
- 28 Sep, 2017 1 commit
-
-
The block in the script installs the packages if we're _not_ on Precise. This was dropped in c17c3f8a ("travis: drop support for Ubuntu Precise") in error.
Carlos Martín Nieto committed
-
- 20 Sep, 2017 1 commit
-
-
Ubuntu Precise is end of life since April 2017. At that point in time, Precise was still the main distro on which Travis CI built upon, with the Trusty-based images still being in a beta state. But since June 21st, Trusty has officially moved out of beta and is now the default image for all new builds. Right now, we build on both old and new images to assure we support both. Unfortunately, this leaves us with the highest minimum version for CMake being 2.8.7, as Precise has no greater version in its repositories. And because of this limitation, we cannot actually use object libraries in our build instructions. But considering Precise is end of life and Trusty is now the new default for Travis, we can and should drop support for this old and unmaintained distribution. And so we do.
Patrick Steinhardt committed
-
- 24 Jul, 2017 3 commits
-
-
Edward Thomson committed
-
Edward Thomson committed
-
Ubuntu trusty has a bug in curl when using NTLM credentials in a proxy, dereferencing a null pointer and causing segmentation faults. Use a custom-patched version of libcurl that avoids this issue.
Edward Thomson committed
-
- 21 Jun, 2017 1 commit
-
-
Some tests of ours require to be running against an SSH server. Currently, we simply run against the SSH server provided and started by Travis itself. As our Linux tests run in a sudo-less environment, we have no control over its configuration and startup/shutdown procedure. While this has been no problem until now, it will become a problem as soon as we migrate over to newer Precise images, as the SSH server does not have any host keys set up. Luckily, we can simply set up our own unpriviledged SSH server. This has the benefit of us being able to modify its configuration even in a sudo-less environment. This commit sets up the unpriviledged SSH server on port 2222.
Patrick Steinhardt committed
-
- 13 Jun, 2017 1 commit
-
-
The formulae provided by the homebrew/dupes tap are deprecated since at least April 4, 2017, with formulae having been migrated to homebrew/core. Replace the deprecated reference to "homebrew/dupes/zlib" with only "zlib".
Patrick Steinhardt committed
-
- 12 Jun, 2017 1 commit
-
-
Edward Thomson committed
-
- 24 Feb, 2017 1 commit
-
-
Download mingw-w64 into our build directory and execute it there, don't try to overwrite the system's mingw.
Edward Thomson committed
-
- 31 Oct, 2016 1 commit
-
-
When running a Coverity build, we have to provide an authentication token in order to proof that we are actually allowed to run analysis in the name of a certain project. As this token should be secret, it is only set on the main repository, so when we were requested to run the Coverity script on another repository we do error out. But in fact we do also error out if the Coverity analysis should _not_ be run if there is no authentication token provided. Fix the issue by only checking for the authentication token after determining if analysis is indeed requested.
Patrick Steinhardt committed
-
- 28 Oct, 2016 2 commits
-
-
We used to only execute Coverity analysis on the 'development' branch before commit 998f0016 (Refine build limitation, 2014-01-15), which refined Coverity build limitations. While we do not really use the 'development' branch anymore, it does still make sense to only analyze a single branch, as otherwise Coverity might get confused. Re-establish the restriction such that we only analyze libgit2's 'master' branch. Also fix the message announcing why we do not actually analyze a certain build.
Patrick Steinhardt committed -
Patrick Steinhardt committed
-
- 10 Oct, 2016 1 commit
-
-
Patrick Steinhardt committed
-
- 05 Oct, 2016 2 commits
-
-
The Mac machines have updated their SSH version and so the ssh-keygen format has changed. Ask it for MD5, which is the one that is output as hex.
Carlos Martín Nieto committed -
This lets us see the details of what we're doing instead of just seeing the output of unknown commands in the build output.
Carlos Martín Nieto committed
-
- 24 Jul, 2016 1 commit
-
-
Edward Thomson committed
-
- 23 Jul, 2016 1 commit
-
-
Edward Thomson committed
-
- 07 Jun, 2016 2 commits
-
-
The `git_buf` structure seems to be too complicated to correctly grasp for Coverity. As such, add simpler models trying to guide Coverity and remove false positives related to these functions.
Patrick Steinhardt committed -
The static analysis engine coverity allows for user models overriding how it treats functions when analyzing code. Like this, one can greatly reduce the rate of false positives and thus make it easier to spot actual errors. Add a user model that overrides function models for `git_buf_len` and `git_vector_insert`, which together amount for a majority of false positives.
Patrick Steinhardt committed
-
- 19 Apr, 2016 1 commit
-
-
It takes a bit for the propxy to get ready to accept connections, so start it before the build so we can be reasonably sure that it's going to be ready in time.
Carlos Martín Nieto committed
-