aboutsummaryrefslogtreecommitdiff
path: root/.travis.yml
AgeCommit message (Collapse)Author
2018-04-10travis: use trusty for coverage buildMarcel Raad
This works now and precise is in the process of being decommissioned. Closes https://github.com/curl/curl/pull/2476
2018-03-26travis: enable apt retry on failJay Satiro
This is a workaround for an unsolved travis issue that is causing CI instances to sporadically fail due to 'unable to connect' issues during apt stage. Ref: https://github.com/travis-ci/travis-ci/issues/8507 Ref: https://github.com/travis-ci/travis-ci/issues/9112#issuecomment-376305909
2018-03-22travis-ci: enable -Werror for CMake builds (#2418)Sergei Nikulov
2018-02-28travis: update compiler versionsMarcel Raad
Update clang to version 3.9 and GCC to version 6. Closes https://github.com/curl/curl/pull/2345
2018-02-15travis: add build with iconv enabledDaniel Stenberg
... to verify it builds and works fine. Ref: https://curl.haxx.se/mail/lib-2017-09/0031.html Closes #1872
2017-12-02travis: use pip2 instead of pipJay Satiro
.. since now mac osx image expects pip2 or pip3, and doesn't know pip: 0.01s$ pip install --user cpp-coveralls /Users/travis/.travis/job_stages: line 57: pip: command not found Ref: https://github.com/travis-ci/travis-ci/issues/8829 Closes https://github.com/curl/curl/pull/2133
2017-12-01.travis.yml: added build --with-libsshNikos Mavrogiannopoulos
Signed-off-by: Nikos Mavrogiannopoulos <nmav@redhat.com>
2017-11-30travis: add boringssl buildDaniel Stenberg
Uses a separate build without --enable-debug and no valgrind. The debug option causes far too many warnings in boringssl's headers (C++ comments, trailing commas etc). Valgrind triggers some false positive errors in thread-local data used by boringssl. Closes #2118
2017-11-05travis: add a job with brotli enabledPatrick Monnerat
2017-10-23travis: exit if any steps failMax Dymond
We don't expect any steps to fail in travis. Exit the script if they do. Closes #1966
2017-10-04fuzzer: move to using external curl-fuzzerMax Dymond
Use the external curl-fuzzer repository for fuzzing. Closes #1923
2017-09-18travis: on mac, don't install openssl or libidnDaniel Stenberg
- openssl is already installed and causes warnings when trying to install again - libidn isn't used these days, and homebrew doesn't seem to have a libidn2 package to replace with easily Closes #1895
2017-09-15tests: enable gssapi in travis-ci linux buildIsaac Boukris
Closes https://github.com/curl/curl/pull/1687
2017-09-11travis: add build without HTTP/SMTP/IMAPDaniel Stenberg
2017-09-07travis: add c-ares enabled builds linux + osxDaniel Stenberg
Closes #1868
2017-09-02ossfuzz: Move to C++ for curl_fuzzer.Max Dymond
Automake gets confused if you want to use C++ static libraries with C code - basically we need to involve the clang++ linker. The easiest way of achieving this is to rename the C code as C++ code. This gets us a bit further along the path and ought to be compatible with Google's version of clang.
2017-09-01ossfuzz: moving towards the ideal integrationMax Dymond
- Start with the basic code from the ossfuzz project. - Rewrite fuzz corpora to be binary files full of Type-Length-Value data, and write a glue layer in the fuzzing function to convert corpora into CURL options. - Have supporting functions to generate corpora from existing tests - Integrate with Makefile.am
2017-08-16travis: add metalink to some osx buildsDaniel Stenberg
Closes #1790
2017-08-16coverage: Use two coveralls commands to get lib/vtls resultsMax Dymond
closes #1747
2017-08-14travis: build the examples tooDaniel Stenberg
to make sure they keep building warning-free Closes #1777
2017-08-12travis: test cmake build on tarball tooDaniel Stenberg
Could've prevented #1755
2017-08-10travis: verify "make install"Daniel Stenberg
Help-by: Jay Satiro Closes #1753
2017-08-04travis: explicitly specify distMarcel Raad
This makes the builds more reproducible as travis is currently rolling out trusty as default dist [1]. Specifically, this avoids coverage check failures when trusty is used as seen in [2] until we figure out what's wrong. [1] https://blog.travis-ci.com/2017-07-11-trusty-as-default-linux-is-coming [2] https://github.com/curl/curl/pull/1692 Closes https://github.com/curl/curl/pull/1725
2017-08-04travis: BUILD_TYPE => TDaniel Stenberg
(to make the full line appear nicer on travis web UI)
2017-08-04travis: add osx build with darwinsslDaniel Stenberg
Closes #1706
2017-08-02travis: build osx with libressl tooDaniel Stenberg
2017-08-02travis: build osx with openssl tooDaniel Stenberg
2017-07-12travis: install libidn2Max Dymond
Install libidn2 to increase test coverage (IDN tests) Closes https://github.com/curl/curl/pull/1673
2017-07-12travis: enable warnings also in release modeMarcel Raad
... to get warnings also on Linux/GCC and OSX/clang. Closes https://github.com/curl/curl/pull/1666
2017-07-12travis: install libssh2Max Dymond
Install libssh2 to increase test coverage (SFTP, SCP)
2017-07-07travis: install stunnelDaniel Stenberg
2017-07-07travis: detect and use valgrind for normal buildsDaniel Stenberg
Closes #1653
2017-07-07travis: add SMB, DICT, TELNET torture to coverage testDaniel Stenberg
2017-07-07travis: do more tests in the coverage runDaniel Stenberg
I added a selection of torture and event tests that run "fast enough"
2017-07-04travis: install nghttp2 on linux buildsDaniel Stenberg
Closes #1642
2017-07-04travis.yml: use --enable-werror on debug buildsDaniel Stenberg
... to better detect and fault on compiler warnings/errors Closes #1637
2017-06-21travis: enable typecheck-gcc warningsMarcel Raad
- switch debug and release configurations so that we get an optimized build with GCC 4.3+ as required by typecheck-gcc - enable warnings-as-errors for release builds (which have warnings disabled) Closes https://github.com/curl/curl/pull/1595
2017-06-21ci: whitelist branches to avoid testing feature branches twiceSimon Warta
2017-06-20travis: do the distcheck test build out-of-tree as wellDaniel Stenberg
2017-06-06travis: let some builds *not* use --enable-debugDaniel Stenberg
typecheck-gcc and other things require optimized builds Closes #1544
2017-06-04travis: add coverage, distcheck and cmake buildsDaniel Stenberg
Closes #1534
2017-03-22travis: run tests-nonflaky instead of tests-fullDaniel Stenberg
2016-08-03travis: removed option to rebuild autotool from sourceSergei Nikulov
Fixes #943
2016-08-01travis: fix OSX build by re-installing libtoolSergei Nikulov
Apparently due to a broken homebrew install fixes #934 Closes #939
2016-07-28Revert "travis: Install libtool for OS X builds"Jay Satiro
Didn't work. This reverts commit 50723585ed380744358de054e2a55dccee65dfd7.
2016-07-28travis: Install libtool for OS X buildsJay Satiro
CI is failing due to missing libtoolize, so I'm trying this.
2015-08-21travis.yml: Add OS X testbot.Jactry Zeng
2015-08-20travis: Upgrading to container based buildRémy Léone
http://docs.travis-ci.com/user/migrating-from-legacy Closes #388
2015-03-10.travis.yml: Change CI make test to make test-fullJay Satiro
- Change the continuous integration script to use 'make test-full' instead of just 'make test' so that the diagnostic log output is printed to stdout when a test fails. - Change the continuous integration script to use './configure --enable-debug' instead of just './configure' so that the memory analyzer will work during testing. Prior to this change Travis used its default C test script: ./configure && make && make test
2013-10-21Adding a .travis.yml file to use the travis-ci.orgRémy Léone
From wikipedia: Travis CI is a hosted, distributed continuous integration service used to build and test projects hosted at GitHub. Travis CI is configured by adding a file named .travis.yml, which is a YAML format text file, to the root directory of the GitHub repository. Travis CI automatically detects when a commit has been made and pushed to a GitHub repository that is using Travis CI, and each time this happens, it will try to build the project and run tests. This includes commits to all branches, not just to the master branch. When that process has completed, it will notify a developer in the way it has been configured to do so — for example, by sending an email containing the test results (showing success or failure), or by posting a message on an IRC channel. It can be configured to run the tests on a range of different machines, with different software installed (such as older versions of a programming language, to test for compatibility).
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-23 15:45:35 +0000