summaryrefslogtreecommitdiff
path: root/ci
Commit message (Collapse)AuthorAgeFilesLines
* ci: add ssl proxy testsethomson/https_proxyEdward Thomson2019-06-113-9/+43
| | | | | In theory, we support proxies over HTTPS. Test that we can support this _in fact_.
* ci: test NTLM proxy authentication on UnixEdward Thomson2019-06-101-4/+22
|
* ci: enable SKIP_OFFLINE_TESTS for windowsEdward Thomson2019-06-101-5/+7
|
* ci: test NTLM proxy authentication on WindowsEdward Thomson2019-06-101-4/+19
| | | | | Update our CI tests to start a proxy that requires NTLM authentication; ensure that our WIndows HTTP client can speak NTLM.
* ci: provide more information about OSEdward Thomson2019-02-131-1/+13
| | | | | | | Subtle changes in the host OS can have impacts in the CI system that may be hard to debug. We previously showed the results of `uname` which can be difficult to interpret. Provide more information where available.
* ci: ignore coverity failures in nightly runsEdward Thomson2019-01-282-24/+33
| | | | | Coverity is back but it's only read-only! Agh. Just allow it to fail and not impact the overall job run.
* ci: update poxyproxy, run in quiet modeEdward Thomson2019-01-202-4/+4
| | | | Update the proxy so that we can enable a quiet mode.
* ci: run all invasive tests on windowsEdward Thomson2019-01-191-0/+4
|
* ci: only run invasive tests during nightly runsEdward Thomson2019-01-192-2/+2
|
* ci: clear settings variables in powershellEdward Thomson2019-01-191-0/+5
|
* ci: enable some of the invasive testcasesEtienne Samson2019-01-112-0/+24
|
* tests: PROXY_URL is more accurately PROXY_HOSTEdward Thomson2018-11-282-3/+3
| | | | | | | Change the `GITTEST_REMOTE_PROXY_URL` environment variable to be `GITTEST_REMOTE_PROXY_HOST`, since it is a host:port combination, not an actual URL. (We cannot use a URL here since we may want to include the username:password combination in the constructed URL.)
* Merge pull request #4860 from tiennou/ci/macos-leaksEdward Thomson2018-10-311-1/+1
|\ | | | | CI: Fix macOS leak detection
| * tests: use CLAR_AT_EXIT to check for leaks on macOSEtienne Samson2018-10-301-1/+1
| |
| * clar: provide a way to run some shell before exitingEtienne Samson2018-10-301-1/+1
| |
| * ci: redirect the malloc debugging output to /dev/nullEtienne Samson2018-10-231-1/+1
| |
* | ci: fail if requested test name is not found (unix)Edward Thomson2018-10-261-0/+6
| | | | | | | | | | | | POSIX: the CMakeLists.txt configures the test names; when we query ctest for the test command-line to run, fail if the tests are not found.
* | ci: fail if requested test name is not found (win32)Edward Thomson2018-10-261-2/+7
| | | | | | | | | | | | Win32: The CMakeLists.txt configures the test names; when we query ctest for the test command-line to run, fail if the tests are not found.
* | ci: fail on test failuresethomson/win_ciEdward Thomson2018-10-251-3/+3
| | | | | | | | | | | | PowerShell can _read_ top-level variables in functions, but cannot _update_ top-level variables in functions unless they're explicitly prefixed with `$global`.
* | ci: bind specifically to localhost for proxyEdward Thomson2018-10-211-2/+2
| | | | | | | | | | | | Bind the proxy specifically to 127.0.0.1 instead of all addresses. This is not strictly necessary for operations, but having a potentially open proxy on a network is not a good idea.
* | ci: move configuration yaml to its own directoryEdward Thomson2018-10-214-89/+0
|/ | | | | As the number of each grow, separate the CI build scripts from the YAML definitions.
* ci: use Ninja on macOSEtienne Samson2018-10-191-1/+1
|
* Merge pull request #4812 from libgit2/ethomson/ci-refactorEdward Thomson2018-09-294-37/+71
|\ | | | | CI: refactoring
| * ci: don't stop on failureethomson/ci-refactorEdward Thomson2018-09-292-8/+17
| | | | | | | | Don't stop on test failures; run all the tests, even when a test fails.
| * ci: append -r flag to clar on windowsEdward Thomson2018-09-291-7/+24
| | | | | | | | | | | | Similar to the way we parse the ctest output on POSIX systems, do the same on Windows. This allows us to append the `-r` flag to clar after we've identified the command to run.
| * ci: add SKIP_*_TESTS for windows buildsEdward Thomson2018-09-171-19/+26
| | | | | | | | | | Introduce SKIP_*_TEST variables for Windows builds to match POSIX builds.
| * ci: write test result XMLethomson/clar-xmlEdward Thomson2018-09-111-3/+6
| | | | | | | | Add the clar flags to produce JUnit-style XML output before invocation.
| * Revert "clar: introduce CLAR_XML option"Edward Thomson2018-09-102-5/+3
| | | | | | | | | | This reverts commit a2d73f5643814cddf90d5bf489332e14ada89ab8. Using clar to propagate the XML settings was a mistake.
| * ci: only run the exact named testEdward Thomson2018-09-101-1/+1
| | | | | | | | | | | | | | Our CI test system invokes ctest with the name of the given tests it wishes to invoke. ctest (with the `-R` flag) treats this name as a regular expression. Provide anchors in the regular expression to avoid matching additional tests in this search.
* | ci: rename vsts to azure-pipelinesEdward Thomson2018-09-184-0/+22
|/
* ci: use templates for VSTS buildsEdward Thomson2018-09-063-0/+67
| | | | | Our build YAML is becoming unweildly and full of copy-pasta. Simplify with templates.
* ci: escape xml output path on WindowsEdward Thomson2018-09-061-1/+3
| | | | | CMake treats backslashes as escape characters; use forward slashes for the XML output path.
* ci: write xml during test runsEdward Thomson2018-09-062-3/+3
|
* ci: Correct the status code check so Coverity doesn't force-fail TravisEtienne Samson2018-08-141-1/+1
| | | | | | | | | | | | | | | | | | | | Otherwise you get something like Emitted 525 C/C++ compilation units (100%) successfully 525 C/C++ compilation units (100%) are ready for analysis The cov-build utility completed successfully. Build successfully submitted. Received error code 200 from Coverity travis_time:end:14cf6373:start=1534254309066933889,finish=1534254728190974302,duration=419124040413 The command "if [ -n "$COVERITY" ]; then ../ci/coverity.sh; fi" exited with 1. travis_time:start:01ed61d4 $ if [ -z "$COVERITY" ]; then ../ci/build.sh && ../ci/test.sh; fi travis_time:end:01ed61d4:start=1534254728197560961,finish=1534254728202711214,duration=5150253 The command "if [ -z "$COVERITY" ]; then ../ci/build.sh && ../ci/test.sh; fi" exited with 0. Done. Your build exited with 1.
* ci: enable compilation with "-Werror"Patrick Steinhardt2018-08-061-1/+1
| | | | | | | During the conversion of our CI scripts in bf418f09c (ci: refactor unix ci build/test scripts, 2018-07-14), we accidentally dropped the "-DENABLE_WERROR=ON" switch in our cmake invocation. Re-add it to help us catch compiler warnings early.
* ci: fix location of fuzzer corpora on VSTSPatrick Steinhardt2018-08-031-1/+1
| | | | | | When using VSTS-based builds, we are in a different location than when doing Travis builds. Due to this, the relative path to our fuzzer corpora does not work on VSTS. Fix it by using `${SOURCE_DIR}` instead.
* fuzzers: rename "fuzz" directory to match our stylePatrick Steinhardt2018-08-031-3/+2
| | | | | | | | | | | Our layout uses names like "examples" or "tests" which is why the "fuzz" directory doesn't really fit in here. Rename the directory to be called "fuzzers" instead. Furthermore, we rename the fuzzer "fuzz_packfile_raw" to "packfile_raw_fuzzer", which is also in line with the already existing fuzzer at google/oss-fuzz. While at it, rename the "packfile_raw" fuzzer to instead just be called "packfile" fuzzer.
* fuzzers: add build support and instructionslhchavez2018-08-032-1/+13
| | | | | | This change adds support for building a fuzz target for exercising the packfile parser, as well as documentation. It also runs the fuzzers in Travis to avoid regressions.
* ci: run coverity from travis's cronEdward Thomson2018-07-291-14/+11
| | | | | | Instead of trying to run coverity builds during the regular PR process, run them during a regularly scheduled cron process. These only need to run nightly, so it makes sense to bring them out of the PR process.
* ci: move travis to the new scriptsEdward Thomson2018-07-283-2/+89
|
* ci: use a single setup script for mingwEdward Thomson2018-07-262-24/+9
|
* ci: perform clang builds on LinuxEdward Thomson2018-07-262-2/+3
|
* ci: dissociate test from leaks processEdward Thomson2018-07-261-2/+1
| | | | | | The leaks process is not good about handling children. Ensure that its child is `nohup`ed so that the grandparent shell won't wait for it to exit.
* ci: some additional debuggingEdward Thomson2018-07-261-0/+8
|
* ci: enable leak checking on osxEdward Thomson2018-07-261-0/+2
|
* ci: msvc leak-checkingEdward Thomson2018-07-261-3/+2
|
* ci: xcode leaks leak-checkingEdward Thomson2018-07-261-0/+4
|
* ci: valgrind leak-checkingEdward Thomson2018-07-261-7/+26
|
* ci: introduce vsts buildsEdward Thomson2018-07-261-0/+1
|
* ci: scripts to setup mingw build environmentEdward Thomson2018-07-262-0/+40
|
View Lorry Controller Status