summaryrefslogtreecommitdiff
path: root/ci
Commit message (Collapse)AuthorAgeFilesLines
* ci: pull libssh2 from www.libssh2.orgethomson/ci_libssh2Edward Thomson2021-09-214-6/+4
| | | | | libssh2.org and www.libssh2.org were previously identical; now this is a redirect.
* opts: test GIT_OPT_SET_SSL_CERT_LOCATIONSEdward Thomson2021-08-291-3/+11
| | | | | Include a self-signed certificate for test.libgit2.org:1443 that we can use to verify that GIT_OPT_SET_SSL_CERT_LOCATIONS works.
* ci: stop on test failureEdward Thomson2021-08-291-0/+5
|
* ci: update container versionsEdward Thomson2021-08-236-0/+6
| | | | | Update all the container versions to force a rebuild so that they'll get tagged with latest (due to changes in the CI scripts).
* ci: update centos to find libssh2ethomson/centos_ciEdward Thomson2021-08-211-0/+2
|
* ci: update centos buildsEdward Thomson2021-08-161-1/+2
|
* ci: update centos buildsEdward Thomson2021-08-162-6/+35
|
* ci: update centos buildsEdward Thomson2021-08-151-1/+0
|
* ci: update centos7 and centos8 buildEdward Thomson2021-08-151-1/+3
|
* ci: add centos7 and centos8 docker definitionsEdward Thomson2021-08-152-0/+69
|
* ci: remove the docker entrypointethomson/dockerfileEdward Thomson2021-08-094-19/+12
| | | | | | | | | Omitting an entrypoint.sh to configure the container and instead depending on docker primitives allows us to be more portable. (If a distribution uses a different mechanism for adding users, we need not have multiple entrypoint.sh files or invariants within it; instead we can configure that in the dockerfile itself along with all the other distribution specific components.)
* ci: use GitHub for storing mingw-w64 build dependencyEdward Thomson2021-05-041-2/+2
|
* ci: don't use ninja on macOSEdward Thomson2021-01-151-1/+12
| | | | | | Ninja is not installed by default on the macOS machines; stop trying to use it. Instead use `make -j` which should be roughly equivalent in performance but supported everywhere.
* Change libssh2 version to 1.9.0 on focalMiguel Arroz2020-12-211-3/+3
|
* ci: support multi-arch docker buildsEdward Thomson2020-11-235-8/+18
| | | | | Provide the base to our docker images and run with the QEMU docker support optionally.
* ci: add krb5 to bionic containerEdward Thomson2020-11-231-0/+2
|
* ci: stop using deprecated set-env in GitHub ActionsEdward Thomson2020-11-1811-0/+725
| | | | (And move the ci scripts into the `ci` directory.)
* azure: move build scripts into "azure-pipelines" directoryPatrick Steinhardt2019-07-209-600/+0
| | | | | | | | | | | | Since we have migrated to Azure Pipelines, we have deprecated and subsequentally removed all infrastructure for AppVeyor and Travis. Thus it doesn't make a lot of sense to have the split between "ci/" and "azure-pipelines/" directories anymoer, as "azure-pipelines/" is essentially our only CI. Move all CI scripts into the "azure-pipelines/" directory to have everything centrally located and to remove clutter in the top-level directory.
* tests: execute leak checker via CTest directlyPatrick Steinhardt2019-07-201-26/+2
| | | | | | | | | | | | | | | Right now, we have an awful hack in our test CI setup that extracts the test command from CTest's output and then prepends the leak checker. This is dependent on non-machine-parseable output from CMake and also breaks on various ocassions, like for example when we have spaces in the current path or when the path contains backslashes. Both conditions may easily be triggered on Win32 systems, and in fact they do break our Azure Pipelines builds. Remove the awful hack in favour of a new CMake build option "USE_LEAK_CHECKER". If specifying e.g. "-DUSE_LEAK_CHECKER=valgrind", then we will set up all tests to be run under valgrind. Like this, we can again simply execute ctest without needing to rely on evil sourcery.
* fuzzers: provide test targetsPatrick Steinhardt2019-07-201-3/+1
| | | | | | Instead of having to find the fuzzer executables in our Azure test scripts, provide test targets for each of our fuzzers that will run them with the correct paths.
* ci: build fuzzers on Powershell based build jobsPatrick Steinhardt2019-07-051-1/+1
| | | | | In order to guarantee that our fuzzers build just fine on the Windows platform, let's enable building fuzzers on all Powershell-based builds.
* ci: build with ENABLE_WERROR on WindowsEdward Thomson2019-06-251-1/+1
| | | | Build with -Werror's equivalent (/WX) on MSVC
* ci: add flaky test re-execution on Windowsethomson/flaky_ciEdward Thomson2019-06-241-2/+28
| | | | | | Our online tests are occasionally flaky since they hit real network endpoints. Re-run them up to 5 times if they fail, to allow us to avoid having to fail the whole build.
* ci: add flaky test re-execution on UnixEdward Thomson2019-06-241-7/+32
| | | | | | Our online tests are occasionally flaky since they hit real network endpoints. Re-run them up to 5 times if they fail, to allow us to avoid having to fail the whole build.
* 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.
View Lorry Controller Status