1. 27 Jun, 2021 1 commit
  2. 13 Dec, 2020 1 commit
  3. 09 Jul, 2020 1 commit
    • Add CI support for Memory and UndefinedBehavior Sanitizers · 6a917c04
      This change adds two new build targets: MSan and UBSan. This is because
      even though OSS-Fuzz is great and adds a lot of coverage, it only does
      that for the fuzz targets, so the rest of the codebase is not
      necessarily run with the Sanitizers ever :( So this change makes sure
      that MSan/UBSan warnings don't make it into the codebase.
      
      As part of this change, the Ubuntu focal container is introduced. It
      builds mbedTLS and libssh2 as debug libraries into /usr/local and as
      MSan-enabled libraries into /usr/local/msan. This latter part is needed
      because MSan requires the binary and all its dependent libraries to be
      built with MSan support so that memory allocations and deallocations are
      tracked correctly to avoid false positives.
      lhchavez committed
  4. 16 Jun, 2020 1 commit
    • Introduce CI with GitHub Actions · 47fb33ba
      Add CI using GitHub Actions and GitHub Packages:
      
      * This moves our Linux build containers into GitHub Packages; we will
        identify the most recent commit that updated the docker descriptions,
        and then look for a docker image in libgit2's GitHub Packages registry
        for a container with the tag corresponding to that description.  If
        there is not one, we will build the container and then push it to
        GitHub Packages.
      
      * We no longer need to manage authentication with our own credentials or
        PAT tokens.  GitHub Actions provides a GITHUB_TOKEN that can publish
        artifacts, packages and commits to our repository within a workflow
        run.
      
      * We will use a matrix to build our various CI steps.  This allows us
        to keep configuration in a single place without multiple YAML files.
      Edward Thomson committed
  5. 11 Jun, 2020 1 commit
  6. 06 Jun, 2020 5 commits
  7. 17 Mar, 2020 1 commit
  8. 13 Mar, 2020 4 commits
  9. 02 Mar, 2020 1 commit
  10. 01 Mar, 2020 1 commit
  11. 19 Feb, 2020 1 commit
    • azure: docker: set up HOME variable to fix Coverity builds · 6efe3d35
      In commit 01a83406 (azure: docker: fix ARM builds by replacing gosu(1),
      2020-02-18), we've switched our entrypoint from gosu(1) to use sudo(1)
      instead to fix our ARM builds. The switch introduced an incompatibility
      that now causes our Coverity builds to fail, as the "--preserve-env"
      switch will also keep HOME at its current value. As a result, Coverity
      now tries to set up its configuration directory in root's home
      directory, which it naturally can't write to.
      
      Fix the issue by adding the "--set-home" flag to sudo(1).
      Patrick Steinhardt committed
  12. 18 Feb, 2020 4 commits
  13. 07 Feb, 2020 7 commits
  14. 04 Feb, 2020 2 commits
  15. 24 Jan, 2020 4 commits
  16. 24 Nov, 2019 5 commits