3party/protobuf-c
0
0
Fork 0
mirror of https://github.com/protobuf-c/protobuf-c.git synced 2025-01-16 12:12:52 +08:00
Code Issues Projects Releases Wiki Activity
protobuf-c/.travis.yml

30 lines
889 B
YAML
Raw Normal View History

.travis.yml: fix 'language' declaration It turns out that in YAML, language: c language: cpp Actually means: language: cpp I'm not sure if travis-ci actually supports providing a list of values for the 'language' parameter, but let's try it anyway.
2014-09-05 14:35:50 -04:00
language:
- c
- cpp
Add a travis-CI config file
2013-11-17 23:58:13 -08:00
.travis.yml: install protobuf 2.5.0 from source The travis-ci environment is based on Ubuntu 12.04 LTS, which has an older protobuf version (2.4.1). We need to depend on features that are only available in 2.5.0 (and, later, 2.6.0), so instead of satisfying the protobuf build dependencies from the Ubuntu repository, download and install our own copy of protobuf. The travis-ci build from this commit should succeed, since we are compatible with protobuf 2.5.0. Based on a patch from Ilya Lipnitskiy.
2014-09-05 14:00:45 -04:00
env:
- PROTOBUF_VERSION=2.5.0
.travis.yml: test on both gcc and clang
2014-03-31 17:47:29 -04:00
compiler:
- gcc
- clang
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: install protobuf 2.5.0 from source The travis-ci environment is based on Ubuntu 12.04 LTS, which has an older protobuf version (2.4.1). We need to depend on features that are only available in 2.5.0 (and, later, 2.6.0), so instead of satisfying the protobuf build dependencies from the Ubuntu repository, download and install our own copy of protobuf. The travis-ci build from this commit should succeed, since we are compatible with protobuf 2.5.0. Based on a patch from Ilya Lipnitskiy.
2014-09-05 14:00:45 -04:00
- sudo apt-get -q install valgrind lcov
.travis.yml: enable code coverage checks and upload data to coveralls.io
2014-06-02 18:04:35 -04:00
- sudo pip install cpp-coveralls
.travis.yml: install protobuf 2.5.0 from source The travis-ci environment is based on Ubuntu 12.04 LTS, which has an older protobuf version (2.4.1). We need to depend on features that are only available in 2.5.0 (and, later, 2.6.0), so instead of satisfying the protobuf build dependencies from the Ubuntu repository, download and install our own copy of protobuf. The travis-ci build from this commit should succeed, since we are compatible with protobuf 2.5.0. Based on a patch from Ilya Lipnitskiy.
2014-09-05 14:00:45 -04:00
- wget https://protobuf.googlecode.com/svn/rc/protobuf-$PROTOBUF_VERSION.tar.gz
- tar xf protobuf-$PROTOBUF_VERSION.tar.gz
- ( cd protobuf-$PROTOBUF_VERSION && ./configure && make -j2 && sudo make install )
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: enable code coverage checks and upload data to coveralls.io
2014-06-02 18:04:35 -04:00
- ./configure --enable-valgrind-tests && make distcheck DISTCHECK_CONFIGURE_FLAGS="--enable-valgrind-tests" VERBOSE=1 && make clean
- if [ "$CC" = "gcc" ]; then ./configure --enable-code-coverage && make && make check; fi
after_success:
- if [ "$CC" = "gcc" ]; then cpp-coveralls --build-root . --exclude t/ --exclude /usr/include; fi
Reference in New Issue Copy Permalink