protobuf-c/.travis.yml

language: c
language: cpp

before_install:
    - sudo apt-get update -qq

install:
    - sudo apt-get -q install protobuf-compiler libprotobuf-dev libprotoc-dev
      valgrind

script:
    - ./autogen.sh
    - ./configure && make distcheck VERBOSE=1 && make clean
    - ./configure --enable-valgrind-tests && make distcheck
      DISTCHECK_CONFIGURE_FLAGS="--enable-valgrind-tests" VERBOSE=1
.travis.yml: add back "language: c" of course, protobuf-c uses both C and C++. 2014-01-14 13:52:21 -05:00			`language: c`
.travis.yml: use system protobuf packages and build using distcheck the change that required protobuf >= 2.5.0 has been reverted, so there's no need to build protobuf from source. use the system protobuf packages instead. also use distcheck to build and check the distribution. this will run the test suite and perform various other checks. it will also perform a VPATH build using the distribution tarball, which will catch any files present in the git repository but inadvertently not distributed in the tarball. also test the build when configured with "--enable-rpc". 2013-11-18 14:35:52 -05:00			`language: cpp`
Add a travis-CI config file 2013-11-17 23:58:13 -08:00
			`before_install:`
.travis.yml: use system protobuf packages and build using distcheck the change that required protobuf >= 2.5.0 has been reverted, so there's no need to build protobuf from source. use the system protobuf packages instead. also use distcheck to build and check the distribution. this will run the test suite and perform various other checks. it will also perform a VPATH build using the distribution tarball, which will catch any files present in the git repository but inadvertently not distributed in the tarball. also test the build when configured with "--enable-rpc". 2013-11-18 14:35:52 -05:00			`- sudo apt-get update -qq`
Add a travis-CI config file 2013-11-17 23:58:13 -08:00
			`install:`
.travis.yml: use system protobuf packages and build using distcheck the change that required protobuf >= 2.5.0 has been reverted, so there's no need to build protobuf from source. use the system protobuf packages instead. also use distcheck to build and check the distribution. this will run the test suite and perform various other checks. it will also perform a VPATH build using the distribution tarball, which will catch any files present in the git repository but inadvertently not distributed in the tarball. also test the build when configured with "--enable-rpc". 2013-11-18 14:35:52 -05:00			`- sudo apt-get -q install protobuf-compiler libprotobuf-dev libprotoc-dev`
.travis.yml: install valgrind on the CI VM 2013-12-03 10:36:14 -08:00			`valgrind`
Add a travis-CI config file 2013-11-17 23:58:13 -08:00
			`script:`
.travis.yml: use system protobuf packages and build using distcheck the change that required protobuf >= 2.5.0 has been reverted, so there's no need to build protobuf from source. use the system protobuf packages instead. also use distcheck to build and check the distribution. this will run the test suite and perform various other checks. it will also perform a VPATH build using the distribution tarball, which will catch any files present in the git repository but inadvertently not distributed in the tarball. also test the build when configured with "--enable-rpc". 2013-11-18 14:35:52 -05:00			`- ./autogen.sh`
.travis.yml: add VERBOSE=1 to make flags in order to log test failures "As with the serial harness above, by default one status line is printed per completed test, and a short summary after the suite has completed. However, standard output and standard error of the test are redirected to a per-test log file, so that parallel execution does not produce intermingled output. The output from failed tests is collected in the test-suite.log file. If the variable ‘VERBOSE’ is set, this file is output after the summary." (http://www.gnu.org/software/automake/manual/html_node/Parallel-Test-Harness.html) 2014-01-14 13:39:33 -05:00			`- ./configure && make distcheck VERBOSE=1 && make clean`
.travis.yml: add a travis build entry to run tests under valgrind Makefile.am: add valgrind to the AM_TESTS_ENVIRONMENT configure.ac: enable valgrind testing option for ./configure m4/valgrind-tests.m4: enable tracing children for libtool wrapper script compatibility, but ignore standard binaries in /usr or /bin 2013-12-03 10:26:51 -08:00			`- ./configure --enable-valgrind-tests && make distcheck`
.travis.yml: remove "make clean" at end of build script 2014-01-14 13:51:30 -05:00			`DISTCHECK_CONFIGURE_FLAGS="--enable-valgrind-tests" VERBOSE=1`