1. 22 Jan, 2019 1 commit
  2. 04 Jan, 2019 1 commit
  3. 28 Jul, 2018 2 commits
  4. 27 Jul, 2018 1 commit
  5. 26 Jul, 2018 2 commits
  6. 06 Jun, 2018 8 commits
  7. 11 Apr, 2018 3 commits
  8. 12 Jan, 2018 1 commit
    • scripts: add backporting script · 0b3d8592
      This adds a simple script for backporting pull requests to older
      branches. It accepts as parameters a list of pull request numbers which
      whose commits are to be cherry-picked. The identification of PRs
      currently happens by using the commit message of the merge of the PR,
      which should conform to the message "Merge pull request #<PR>".
      
      While the heuristic works in practice, we could instead also use the
      direct references from GitHub via "pull/#<PR>/head". This requires the
      user to have all these references fetched, though, so we can just use
      the current heuristic until we experience any issues with that.
      Patrick Steinhardt committed
  9. 03 Jan, 2018 3 commits
    • tests: create new test target for all SSH-based tests · 5874e151
      Some tests shall be run against our own SSH server we spin up in Travis.
      As those need to be run separate from our previous tests which run
      against git-daemon, we have to do this in a separate step. Instead of
      bundling all that knowledge in the CI script, move it into the test
      build instructions by creating a new test target.
      Patrick Steinhardt committed
    • tests: online::clone: inline creds-test with nonexistent URL · 54a1bf05
      Right now, we test our credential callback code twice, once via SSH on
      localhost and once via a non-existent GitHub repository. While the first
      URL makes sense to be configurable, it does not make sense to hard-code
      the non-existing repository, which requires us to call tests multiple
      times. Instead, we can just inline the URL into another set of tests.
      Patrick Steinhardt committed
    • tests: online::clone: construct credential-URL from environment · fea60920
      We support two types of passing credentials to the proxy, either via the
      URL or explicitly by specifying user and password. We test these types
      by modifying the proxy URL and executing the tests twice, which is
      in fact unnecessary and requires us to maintain the list of environment
      variables and test executions across multiple CI infrastructures.
      
      To fix the situation, we can just always pass the host, port, user and
      password to the tests. The tests can then assemble the complete URL
      either with or without included credentials, allowing us to test both
      cases in-process.
      Patrick Steinhardt committed
  10. 06 Nov, 2017 1 commit
    • appveyor: build examples · 0b98a66b
      By default, CMake will not build our examples directory. As we do not
      instruct either the MinGW or MSVC builds on AppVeyor to enable building
      these examples, we cannot verify that those examples at least build on
      Windows systems.
      
      Fix that by passing `-DBUILD_EXAMPLES=ON` to AppVeyor's CMake
      invocation.
      Patrick Steinhardt committed
  11. 31 Oct, 2017 2 commits
  12. 06 Oct, 2017 1 commit
  13. 28 Sep, 2017 1 commit
  14. 20 Sep, 2017 1 commit
    • travis: drop support for Ubuntu Precise · c17c3f8a
      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.
      Patrick Steinhardt committed
  15. 24 Jul, 2017 3 commits
  16. 21 Jun, 2017 1 commit
    • travis: cibuild: set up our own sshd server · 06619904
      Some tests of ours require to be running against an SSH server.
      Currently, we simply run against the SSH server provided and started by
      Travis itself. As our Linux tests run in a sudo-less environment, we
      have no control over its configuration and startup/shutdown procedure.
      While this has been no problem until now, it will become a problem as
      soon as we migrate over to newer Precise images, as the SSH server does
      not have any host keys set up. Luckily, we can simply set up our own
      unpriviledged SSH server. This has the benefit of us being able to
      modify its configuration even in a sudo-less environment.
      
      This commit sets up the unpriviledged SSH server on port 2222.
      Patrick Steinhardt committed
  17. 13 Jun, 2017 1 commit
  18. 12 Jun, 2017 1 commit
  19. 24 Feb, 2017 1 commit
  20. 31 Oct, 2016 1 commit
    • coverity: check for Coverity token only if necessary · 18c18e3d
      When running a Coverity build, we have to provide an
      authentication token in order to proof that we are actually
      allowed to run analysis in the name of a certain project. As this
      token should be secret, it is only set on the main repository, so
      when we were requested to run the Coverity script on another
      repository we do error out. But in fact we do also error out if
      the Coverity analysis should _not_ be run if there is no
      authentication token provided.
      
      Fix the issue by only checking for the authentication token after
      determining if analysis is indeed requested.
      Patrick Steinhardt committed
  21. 28 Oct, 2016 2 commits
  22. 10 Oct, 2016 1 commit
  23. 05 Oct, 2016 1 commit