summaryrefslogtreecommitdiff
path: root/.travis.yml
Commit message (Collapse)AuthorAgeFilesLines
* travis/docker: Various improvementsJulian Andres Klode2017-07-021-1/+1
| | | | | | | | | | | - Use a tmpfs for /tmp - not really a benefit here, except for travis as it's writing less now. - Use the fastly CDN - about twice as fast as ftp.de, and seems more stable than cloudfront - Run apt-get clean to keep container smaller - should not be needed really, but let's just do it. Gbp-Dch: ignore
* Switch to 'http' as the default https methodJulian Andres Klode2017-06-301-1/+1
| | | | | The old curl based method is still available as 'curl', 'curl+http', and 'curl+https'.
* travis: Switch to DockerJulian Andres Klode2017-06-301-26/+13
| | | | | | | | | | | | | | | | | This runs parallel builds on docker, based on debian:testing docker images, with ccache enabled and parallel running of the test suite (ccache supports coverage builds these days, and parallel testing just needs unbuffer to handle the stty stuff) This is a huge step up from building on a mix of trusty, wily, and xenial. Most importantly, coverage now correctly detects partial covered lines instead of just reporting almost all of them as fully covered. We use ftp.de.debian.org as deb.debian.org backed by Amazon 503s too often. Gbp-Dch: ignore
* Fix test suite and enable non-curl testing on travis, shippableJulian Andres Klode2017-06-281-0/+1
| | | | Gbp-Dch: ignore
* methods: Add HTTPS support to http method, using GnuTLSJulian Andres Klode2017-06-281-1/+1
| | | | | | | | | | | | | | The http method will eventually replace the curl-based https method, but for now, this is an opt-in experiment that can be enabled by setting Dir::Bin::Methods::https to "http". Known issues: - We do not support HTTPS proxies yet - We do not support proxying HTTPS connections yet (CONNECT) - IssuerCert and SslForceVersion are unsupported Gbp-Dch: Full
* travis: Do not build documentation in root jobJulian Andres Klode2017-01-241-3/+3
| | | | | | | This speeds up testing things as root, which is good, because we usually test as user. Gbp-Dch: ignore
* travis: Run test suites for root and user in separate build jobsJulian Andres Klode2017-01-241-2/+5
| | | | | | | | This hopefully cuts down on the test time. Optimally, we'd just have one build job and parallize, but that requires a tty or something, probably due to GNU parallel? Gbp-Dch: ignore
* travis: Move codecov from after_success to after_scriptJulian Andres Klode2016-10-041-1/+1
| | | | | | We always want to run codecov test, even if there are spurious failures. We should really work around those failures more, though, it is starting to annoy me.
* travis: Add coverage testing using codecov.ioJulian Andres Klode2016-09-111-1/+7
| | | | | | | | | This allows fully automated code coverage testing, which is basically awesome. To allow the methods and solvers and stuff which run as _apt to write to our build directory, we need to adjust the permissions a bit, but otherwise it's OK. Gbp-Dch: ignore
* travis: use ninja and ccache for buildingJulian Andres Klode2016-09-111-5/+6
| | | | | | | This cleans up the output a bit, it should also improve performance, but unfortunately, this does not really seem to be the case. Gbp-Dch: ignore
* test, travis: Quieter testing with a new -qq modeJulian Andres Klode2016-08-291-4/+3
| | | | | | | | | | | | | | | Introduce a new -qq mode for our integration test framework, and make travis use it. The new -qq mode sets MSGLEVEL to 1. In MSGLEVEL=1, no messages are generated for passed tests, and all testcase filenames are printed in the same line. Also install first in travis, do not ls the installed output and run the install with chronic, so we only get output if it failed. Gbp-Dch: ignore
* prepare-release: Use equivs and gdebi-core for travis depsJulian Andres Klode2016-08-191-1/+1
| | | | | | | | Our previous hack did not really support or groups and other more advanced dependency types. This hack basically removes build profiles, and the @-type depends for tests, and otherwise converts the deps to a package which is then installed via gdebi.
* ctest: show test output in case of failuresDavid Kalnischkies2016-08-121-1/+1
| | | | | | | | | | ctest as run by cmake by default does not show the output of the tests even if the tests failed. In terms of our tests it could be handy to set it always, but unfortunately it seems like cmake doesn't allow it if the internet is to be believed, so lets enable it at least while building packages and on travis. Gbp-Dch: Ignore
* CMake: Add unit testsJulian Andres Klode2016-08-101-0/+1
| | | | | | | | Add support for our GTest based unit tests. By default, CMake will look in /usr/src/gtest for the external GTest project, but this can be overriden by defining GTEST_ROOT when invoking cmake. Gbp-Dch: ignore
* CMake: Switch integration tests and travis overJulian Andres Klode2016-08-061-2/+8
| | | | | | This early support seems a bit hacky, but it's a hard switch: The integration tests do not understand the old build system anymore afterwards. I don't really like that.
* Revert "travis: use gcc-5 instead of gcc(-4.8)"David Kalnischkies2016-06-291-3/+1
| | | | | | | | | | | | | | | This reverts commit 2b8221d66a8284042fc53c7bbb14bb9750e9137f. Avoiding the use of GCC >= 5 stuff lets use go back to 4.8 simplifying the travis setup again as well as reducing the backport requirements in general. This is possible because the std::get_time use requiring GCC >= 5 in 9febc2b238e1e322dce1f94ecbed46d595893b52 was replaced by handrolling it in 1d742e01470bba27715a8191c50adde4b39c2f19, so the remaining uses are just small conviniences we can do without. Gbp-Dch: Ignore
* travis: use gcc-5 instead of gcc(-4.9)David Kalnischkies2016-05-281-1/+3
| | | | | | | | | | | | | | | | | The std::put_time and std::get_time introduced in 9febc2b238e1e322dce1f94ecbed46d595893b52 are part of C++11, but not implemented in GCC until version 5. std::put_time could actually be worked around via using the facets put() directly, but get() isn't implemented so that doesn't really help. We require various tools from wily (which also means we can't build apt on Debian stable) already, so requiring gcc-5 is just one more instead of a big step [and an ignoreable change for changelog anyhow]. It also helps in testing what will actually be used (in terms of the c++11 std ABI) instead of the old ABI. Git-Dch: Ignore
* Fix bug where the problemresolve can put a pkg into a heisenstateMichael Vogt2016-03-151-1/+1
| | | | | | | | | | | | | | | | The problemresolver will set the candidate version for pkg P back to the current version if it encounters an impossible to satisfy critical dependency on P. However it did not set the State of the package back as well which lead to a situation where P is neither in Keep,Install,Upgrade,Delete state. Note that this can not be tested via the traditional sh based framework. I added a python-apt based test for this. LP: #1550741 [jak@debian.org: Make the test not fail if apt_pkg cannot be imported]
* travis: pull liblz4-dev from wilyJulian Andres Klode2016-01-071-3/+3
|
* .travis.yml: Switch to new trusty machinesJulian Andres Klode2015-12-111-3/+1
| | | | | | Yay, newer server Gbp-Dch: ignore
* travis: move 'make' into the install targetDavid Kalnischkies2015-11-041-1/+1
| | | | | | | This auto-collapses the output and doesn't run the tests if we compiling fails as a bonus. Git-Dch: Ignore
* .travis.yml: Add pinned vivid for gettext and clean up a bitJulian Andres Klode2015-10-111-2/+4
| | | | | | | | | This adds a vivid pinned to -1, cleans up the file a bit by removing duplicate commands, and finally installs gettext with a new apt-get run that is passed -t vivid. The syntax for the pinning is some weird YAML stuff I don't want to think about...
* travis: use -q mode to reduce the verbosity greatlyDavid Kalnischkies2015-08-311-2/+2
| | | | Git-Dch: Ignore
* tavis: run testcases a second time, but as rootDavid Kalnischkies2015-08-311-4/+10
| | | | Git-Dch: Ignore
* Re-add support for G++ 4.8 and configure travis to use itJulian Andres Klode2015-08-171-3/+5
| | | | | | This makes tests work again! Gbp-Dch: ignore
* travis: add ppa:ubuntu-toolschain-r/test as source for gcc-5David Kalnischkies2015-08-121-1/+5
| | | | | | | | This makes travis-ci able to run our tests again. Sometimes. If it doesn't spontaneously fails with internal gcc errors… Git-Dch: Ignore
* parse debian/tests/control for test dependenciesDavid Kalnischkies2014-08-261-1/+0
| | | | | | | | Our integration tests need some additional dependencies to run and function correctly, but while multiple places run them, there is no need to also specify the these dependencies in multiple places. Git-Dch: Ignore
* fix test/integration/test-apt-ftparchive-cachedb-lp1274466 in travisMichael Vogt2014-06-101-1/+1
|
* extract travis installs from build-depends automaticallyDavid Kalnischkies2014-04-161-1/+2
| | | | | | | | I forgot to add libgtest-dev to the list of packages to install on travis, so this slightly hacky oneliner might prevent us from having the same problem again if we happen to change dependencies again. Git-Dch: Ignore
* tests: install --no-install-recommends and stunnel4 for travisDavid Kalnischkies2013-10-031-1/+1
| | | | | | stunnel4 is required for https tests Git-Dch: Ignore
* add missing "make test" for travisMichael Vogt2013-07-261-1/+1
|
* build tree firstMichael Vogt2013-07-261-1/+1
|
* make setup in travis.yml a bit more verboseMichael Vogt2013-07-261-2/+2
|
* fix travis.ymlMichael Vogt2013-07-251-1/+1
|
* add .travis.ymlMichael Vogt2013-07-251-0/+5
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2024-11-01 14:36:36 +0000