|
6e748130
|
2018-01-10T15:13:23
|
|
travis: we use bintray's own key for signing
The VM on Travis apparently will still proceed, but it's good practice.
|
|
da9898ab
|
2018-01-10T12:33:56
|
|
travis: fetch trusty dependencies from bintray
The trusty dependencies are now hosted on Bintray.
|
|
8999f6ac
|
2017-06-07T11:01:28
|
|
travis: build sources with tracing enabled
Our tracing architecture is not built by default, causing the Travis CI
to not execute some code and skip several tests. As AppVeyor has already
enabled the tracing architecture when building the code, we should do
the same for Travis CI to have this code being tested on macOS and
Linux.
Add "-DENABLE_TRACE=ON" to our release-build options of Travis.
|
|
|
45c6efd5
|
2017-10-30T15:40:44
|
|
travis: grab pgp key from www.edwardthomson.com
Getting the key from the MIT keyserver is surprisingly unreliable.
Try getting it from my website instead...
|
|
|
9dc21efd
|
2017-10-07T00:10:06
|
|
travis: add custom apt sources
Move back to Travis's VM infrastructure for efficiency.
|
|
|
c17c3f8a
|
2017-09-06T08:04:19
|
|
travis: drop support for Ubuntu Precise
Ubuntu Precise is end of life since April 2017. At that point in time,
Precise was still the main distro on which Travis CI built upon, with
the Trusty-based images still being in a beta state. But since June
21st, Trusty has officially moved out of beta and is now the default
image for all new builds. Right now, we build on both old and new images
to assure we support both.
Unfortunately, this leaves us with the highest minimum version for CMake
being 2.8.7, as Precise has no greater version in its repositories. And
because of this limitation, we cannot actually use object libraries in
our build instructions. But considering Precise is end of life and
Trusty is now the new default for Travis, we can and should drop support
for this old and unmaintained distribution. And so we do.
|
|
|
414a3384
|
2017-08-25T17:36:59
|
|
travis: error on compiler warnings
One of our goals is to have our code free of any warnings. Due to the
recent switch to Ubuntu 14.04 on Travis, the last warning regarding some
preprocessor-magic in the curl-headers has been fixed and as such, the
goal of zero warnings is now reached for Travis CI. In order to avoid
introducing new warnings via pull requests, we can now enable building
with `-Werror` and turn compiler warnings into errors instead, causing
the CI jobs to fail.
This build does so by passing the newly introdcued `-DENABLE_WERROR`
flag to CMake for all Travis jobs.
|
|
|
4da38193
|
2017-07-24T13:10:43
|
|
travis: use trusty
|
|
|
f031e20b
|
2017-07-23T03:41:52
|
|
travis: build with patched libcurl
Ubuntu trusty has a bug in curl when using NTLM credentials in a proxy,
dereferencing a null pointer and causing segmentation faults. Use a
custom-patched version of libcurl that avoids this issue.
|
|
|
7c8d460f
|
2017-04-21T07:58:46
|
|
travis: upgrade container to Ubuntu 14.04
Ubuntu 12.04 (Precise Pangolin) reaches end of life on April 28th, 2017.
As such, we should update our build infrastructure to use the next
available LTS release, which is Ubuntu 14.04 LTS (Trusty Tahr). Note
that Trusty is still considered beta quality on Travis. But considering
we are able to correctly build and test libgit2, this seems to be a
non-issue for us.
Switch over our default distribution to Trusty. As Precise still has
extended support for paying customers, add an additional job which
compiles libgit2 on the old release.
|
|
|
0334bf4b
|
2016-10-28T14:57:54
|
|
travis: do not allow valgrind failures
Our valgrind jobs haven't been failing for several builds by now.
This indicates that our tests are sufficiently stable when
running under valgrind. As such, any failures reported by
valgrind become interesting to us and shouldn't be ignored when
causing a build to fail.
Remove the valgrind job from the list of allowed failures.
|
|
b1093e62
|
2016-03-09T19:01:33
|
|
Remove CI support for mingw32
The tests have never run successfully and we do have successful builds
of mingw-w64, so remove these CI builds which do not add value.
|
|
da033560
|
2016-02-28T11:34:36
|
|
travis ci: enable debug pool for valgrind builds
|
|
b48dfe0b
|
2015-06-27T14:54:19
|
|
Always install valgrind via the apt addon.
|
|
76d7c359
|
2015-06-26T17:58:45
|
|
Fast builds?
|
|
|
ca183d27
|
2015-05-22T17:44:28
|
|
travis: build maint branches
|
|
8f426d7d
|
2014-06-09T11:43:25
|
|
Win32: Enable WinHTTP for MinGW
|
|
feb0e022
|
2015-02-19T12:14:06
|
|
tests: separate INVASIVE filesystem tests
Introduce GITTEST_INVASIVE_FS_STRUCTURE for things that are invasive
to your filesystem structure (like creating folders at your filesystem
root) and GITTEST_INVASIVE_FS_SIZE for things that write lots of data.
|
|
|
1dbb74ba
|
2014-11-22T18:46:17
|
|
Travis: do non-threadsafe builds
When flipping the default to threadsafe, we never made sure that the
tests were building non-threadsafe variants. Specify which thead-safety
we want for each.
|
|
|
60f3e876
|
2014-11-22T18:42:00
|
|
Travis: move the valgrind run to allowed_failures
We don't need to know the result of the travis run before determining
whether we want to consider the merge as successful.
|
|
|
6340e8f5
|
2014-09-17T15:52:01
|
|
travis: another attempt at multiple allowed failures
It looks like what Travis wants is a list of hashes, rather than a hash
with a list.
|
|
|
5c22c4a2
|
2014-09-17T15:32:21
|
|
travis: fix allowed failures list
|
|
|
570452e3
|
2014-09-16T17:38:03
|
|
travis: run valgrind only once
Instead of running valgrind on each job, half of which are in release
mode and don't have much usable information for valgrind, perform an
debug build as part of allowed_failures and run valgrind on that one,
which should speed up the feedback we get from the builds.
|
|
|
c61dc1a9
|
2014-06-25T17:12:44
|
|
travis: build the master branch
We need to tell Travis to build the master branch or it won't build it
or the pull requests.
|
|
|
72303307
|
2014-05-21T12:45:22
|
|
travis: build on osx too
|
|
|
f5fc63bc
|
2014-04-30T10:55:58
|
|
Don't exclude libssh2 from MinGW
It reportedly works. It does not however work when cross-compiling on
Travis, so let's disable it there.
This fixes #2311.
|
|
f1c16d0e
|
2014-01-13T15:18:13
|
|
Tweak travis secure config
|
|
|
9bf17d2c
|
2014-01-13T14:11:14
|
|
Add coverity-scan script
|
|
90a8ad63
|
2013-08-19T00:18:44
|
|
ci: Make Valgrind run on Travis
|
|
|
5be622fb
|
2013-08-11T01:37:44
|
|
Test SSH in travis
Set up the ssh credentials so we are able to talk to localhost and
issue git commands. Move to use a script, as the command list is
getting somewhat long.
While here, delay installing valgrind until we need it, as it and its
dependencies are by far the largest downloads and this allows us to
start compiling (and failing) faster and we only incur this cost when
the test suite runs successfully.
|
|
|
fb42a22e
|
2013-04-29T02:15:51
|
|
travis: test push
Create a test repository in the VM and set up git-daemon so we can
use it to test the push code.
|
|
|
2c7f7a66
|
2013-03-25T17:35:36
|
|
http: Support 302 Found (arrbee did most of the work)
|
|
c2ea65ee
|
2013-03-25T21:22:57
|
|
clar: Disable online tests. By now.
|
|
|
d768f9ad
|
2013-03-10T21:37:09
|
|
travis: join-less notifications
|
|
|
f42beff7
|
2013-01-25T23:35:04
|
|
Expand valgrind suppressions even more for libssl, libcrypto
|
|
|
5026aec2
|
2013-01-25T23:24:13
|
|
Improve valgrind suppressions
|
|
|
ced8eff1
|
2013-01-06T17:21:37
|
|
travis: Only run Valgrind when all tests pass
|
|
|
09556895
|
2013-01-06T14:40:32
|
|
travis: Include the online suite when running against Travis
|
|
|
a2188625
|
2013-01-03T02:35:23
|
|
Remove the submodule from travis
|
|
|
afb18116
|
2013-01-03T01:04:18
|
|
/deal with it
|
|
|
a44f2e9e
|
2013-01-02T22:26:34
|
|
Try it like this...
|
|
|
e229c048
|
2013-01-02T21:25:32
|
|
Fuck you CMake
|
|
|
0df41675
|
2013-01-02T21:22:19
|
|
Submodule checkout
|
|
cedc15af
|
2012-12-20T03:51:06
|
|
Mark travis build as failed if any test fails
|
|
|
37ac4436
|
2012-12-14T03:02:33
|
|
travis: update the apt-get db
|
|
|
ed6a4187
|
2012-12-06T17:39:56
|
|
travis: Try this key
|
|
|
7be7b42f
|
2012-12-06T17:08:53
|
|
travis: Fix this hook
|
|
|
79c649e4
|
2012-12-06T15:52:15
|
|
travis: Campfire notifications. Of course.
|
|
|
e30c052c
|
2012-11-01T23:01:24
|
|
LEAAAVE ME ALOOOONEEE
|
|
|
a75770fe
|
2012-10-10T14:57:05
|
|
tests: add a test for tag autofollow behaviour
Also tell ctest and valgrind to run libgit2_clar with '-iall' so we
run the network tests in travis.
|
|
064ee42d
|
2012-09-04T15:54:33
|
|
travis: use a valgrind suppressions file
We don't care about the supposed zlib errors, and the leak from
giterr_set isn't interesting, as it gets freed each time an error is
set.
Give valgrind a suppressions file so it doesn't tell us about them.
|
|
|
034ccc76
|
2012-07-24T19:07:55
|
|
travis: be more idiomatic with the environment
Instead of putting the compilers in CC, use the travis configuration
to specify them.
Also ask it to send reports to the IRC channel.
|
|
8d711074
|
2012-07-22T19:42:47
|
|
travis: build with both gcc and clang
|
|
|
9f99c5de
|
2012-07-12T21:04:09
|
|
travis: make it run the tests under valgrind
|
|
64ab0ba7
|
2012-05-26T18:23:54
|
|
Enable mingw cross-compile stage in travis-ci
|
|
|
62986ff6
|
2012-05-20T00:46:48
|
|
Add CMake build for examples / add them to Travis
By default, they are still not built, but hopefully, now that Travis is
building them, this will help stave off some of the bitrot.
|
|
|
c2d82a65
|
2012-05-07T12:31:31
|
|
travis: run the tests verbosely
|
|
|
8b9ec201
|
2012-04-29T01:38:36
|
|
Add a travis config file
Teach travis how to build the project.
|
|
|
7ef9f1b5
|
2012-04-02T21:05:45
|
|
Backport .travis.yml
|
|
|
5afe95d2
|
2012-04-02T20:45:04
|
|
travis: Change notify email
|
|
f9abcbdf
|
2012-04-02T00:33:01
|
|
Initial Travis CI build
|