kmx git

Commit	Date	Message
f195395a	2018-10-21T09:16:35	ci: bind specifically to localhost for proxy 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.
4ec597dc	2018-10-21T09:12:43	ci: move configuration yaml to its own directory As the number of each grow, separate the CI build scripts from the YAML definitions.
6a67e42d	2018-10-08T19:33:27	ci: use Ninja on macOS
1621a37d	2018-09-29T13:22:59	Merge pull request #4812 from libgit2/ethomson/ci-refactor CI: refactoring
429c7f11	2018-09-17T20:12:59	ci: don't stop on failure Don't stop on test failures; run all the tests, even when a test fails.
7c9769d9	2018-09-17T19:57:26	ci: append -r flag to clar on windows 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.
d7d0139e	2018-09-18T13:35:25	ci: rename vsts to azure-pipelines
a8301b0c	2018-09-11T15:15:26	ci: add SKIP__TESTS for windows builds Introduce SKIP__TEST variables for Windows builds to match POSIX builds.
fff33a1b	2018-09-10T14:59:20	ci: write test result XML Add the clar flags to produce JUnit-style XML output before invocation.
943181c2	2018-09-10T12:36:51	Revert "clar: introduce CLAR_XML option" This reverts commit a2d73f5643814cddf90d5bf489332e14ada89ab8. Using clar to propagate the XML settings was a mistake.
7e353b7a	2018-09-10T12:27:24	ci: only run the exact named test 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.
6b2d8f09	2018-08-26T18:05:31	ci: use templates for VSTS builds Our build YAML is becoming unweildly and full of copy-pasta. Simplify with templates.
f3f2c45e	2018-08-26T17:12:17	ci: escape xml output path on Windows CMake treats backslashes as escape characters; use forward slashes for the XML output path.
a84863fc	2018-08-26T16:07:32	ci: write xml during test runs
351ca661	2018-08-14T21:26:14	ci: Correct the status code check so Coverity doesn't force-fail Travis 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.
90084657	2018-08-06T09:12:48	ci: enable compilation with "-Werror" 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.
835d6043	2018-08-03T10:01:59	ci: fix location of fuzzer corpora on VSTS 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.
59328ed8	2018-07-19T13:29:46	fuzzers: rename "fuzz" directory to match our style 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.
60e610a2	2018-01-04T15:36:22	fuzzers: add build support and instructions 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.
6b92368c	2018-07-28T22:29:53	ci: run coverity from travis's cron 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.
24b8dd82	2018-07-27T12:31:32	ci: move travis to the new scripts
f7bb4ff8	2018-07-26T15:06:01	ci: use a single setup script for mingw
dc6e80e2	2018-07-26T14:04:19	ci: perform clang builds on Linux
6eb97b6b	2018-07-25T01:04:55	ci: dissociate test from leaks process 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.
230eeda8	2018-07-21T10:49:23	ci: some additional debugging
b00672b9	2018-07-20T19:47:40	ci: enable leak checking on osx
afecd15c	2018-07-20T18:09:38	ci: msvc leak-checking
7f12c123	2018-07-20T17:20:15	ci: xcode leaks leak-checking
6d6700d2	2018-07-20T19:01:55	ci: valgrind leak-checking
67f5304f	2018-07-14T12:42:50	ci: introduce vsts builds
9e588060	2018-07-14T13:03:16	ci: scripts to setup mingw build environment
87342404	2018-07-14T12:35:02	ci: set up a macos host Script to set up dependencies on a macOS build system.
5bb2087b	2018-07-14T12:34:05	ci: setup a linux host Sets up a linux host to prepare for a build.
451b0017	2018-07-14T12:25:32	ci: improved flexibility for citest.sh Refactor citest.sh to enable local testing by developers.
bf418f09	2018-07-14T12:24:40	ci: refactor unix ci build/test scripts
e2cc5b6d	2018-07-14T12:22:47	ci: move tests into citest.ps1 Add citest.ps1 PowerShell script to run the tests.
3b6281fa	2018-07-14T12:22:16	ci: Windows PowerShell build script

f195395a

2018-10-21T09:16:35

ci: bind specifically to localhost for proxy 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.

4ec597dc

2018-10-21T09:12:43

ci: move configuration yaml to its own directory As the number of each grow, separate the CI build scripts from the YAML definitions.

6a67e42d

2018-10-08T19:33:27

ci: use Ninja on macOS

1621a37d

2018-09-29T13:22:59

Merge pull request #4812 from libgit2/ethomson/ci-refactor CI: refactoring

429c7f11

2018-09-17T20:12:59

ci: don't stop on failure Don't stop on test failures; run all the tests, even when a test fails.

7c9769d9

2018-09-17T19:57:26

ci: append -r flag to clar on windows 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.

d7d0139e

2018-09-18T13:35:25

ci: rename vsts to azure-pipelines

a8301b0c

2018-09-11T15:15:26

ci: add SKIP_*_TESTS for windows builds Introduce SKIP_*_TEST variables for Windows builds to match POSIX builds.

fff33a1b

2018-09-10T14:59:20

ci: write test result XML Add the clar flags to produce JUnit-style XML output before invocation.

943181c2

2018-09-10T12:36:51

Revert "clar: introduce CLAR_XML option" This reverts commit a2d73f5643814cddf90d5bf489332e14ada89ab8. Using clar to propagate the XML settings was a mistake.

7e353b7a

2018-09-10T12:27:24

ci: only run the exact named test 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.

6b2d8f09

2018-08-26T18:05:31

ci: use templates for VSTS builds Our build YAML is becoming unweildly and full of copy-pasta. Simplify with templates.

f3f2c45e

2018-08-26T17:12:17

ci: escape xml output path on Windows CMake treats backslashes as escape characters; use forward slashes for the XML output path.

a84863fc

2018-08-26T16:07:32

ci: write xml during test runs

351ca661

2018-08-14T21:26:14

ci: Correct the status code check so Coverity doesn't force-fail Travis 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.

90084657

2018-08-06T09:12:48

ci: enable compilation with "-Werror" 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.

835d6043

2018-08-03T10:01:59

ci: fix location of fuzzer corpora on VSTS 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.

59328ed8

2018-07-19T13:29:46

fuzzers: rename "fuzz" directory to match our style 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.

60e610a2

2018-01-04T15:36:22

fuzzers: add build support and instructions 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.

6b92368c

2018-07-28T22:29:53

ci: run coverity from travis's cron 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.

24b8dd82

2018-07-27T12:31:32

ci: move travis to the new scripts

f7bb4ff8

2018-07-26T15:06:01

ci: use a single setup script for mingw

dc6e80e2

2018-07-26T14:04:19

ci: perform clang builds on Linux

6eb97b6b

2018-07-25T01:04:55

ci: dissociate test from leaks process 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.

230eeda8

2018-07-21T10:49:23

ci: some additional debugging

b00672b9

2018-07-20T19:47:40

ci: enable leak checking on osx

afecd15c

2018-07-20T18:09:38

ci: msvc leak-checking

7f12c123

2018-07-20T17:20:15

ci: xcode leaks leak-checking

6d6700d2

2018-07-20T19:01:55

ci: valgrind leak-checking

67f5304f

2018-07-14T12:42:50

ci: introduce vsts builds

9e588060

2018-07-14T13:03:16

ci: scripts to setup mingw build environment

87342404

2018-07-14T12:35:02

ci: set up a macos host Script to set up dependencies on a macOS build system.

5bb2087b

2018-07-14T12:34:05

ci: setup a linux host Sets up a linux host to prepare for a build.

451b0017

2018-07-14T12:25:32

ci: improved flexibility for citest.sh Refactor citest.sh to enable local testing by developers.

bf418f09

2018-07-14T12:24:40

ci: refactor unix ci build/test scripts

e2cc5b6d

2018-07-14T12:22:47

ci: move tests into citest.ps1 Add citest.ps1 PowerShell script to run the tests.

3b6281fa

2018-07-14T12:22:16

ci: Windows PowerShell build script

thodg/libgit2/ci

ci

Log