1. 10 Dec, 2021 1 commit
  2. 22 Nov, 2021 1 commit
  3. 11 Oct, 2021 13 commits
  4. 07 Oct, 2021 6 commits
    • Kevin Daudt's avatar
      tests: generate and install keys · ff913b49
      Kevin Daudt authored
      abuild requires that a build key is present, so make sure a key is
    • Kevin Daudt's avatar
      tests: add project dir to PATH · 789fca23
      Kevin Daudt authored
      abuild and abump call a few helpers that are expected to be available in
      PATH. As abuild is not installed yet, they are not in the default PATH
      Add the project root dir to $PATH to make sure these helpers can be found.
    • Kevin Daudt's avatar
      tests: set APORTSDIR for abuild tests · 12ba0a14
      Kevin Daudt authored
      If `APORTSDIR` is not set, abuild tries to find it. One way it does this
      is by trying to look at the url for the git remote 'origin'. This fails
      either if there is no git repository, or the git repository has no
      remote called 'origin'.
      Instead of having abuild guess the location, provide it by exporting
    • Kevin Daudt's avatar
      ci: add job to run tests · d4af7cd4
      Kevin Daudt authored
      This uses the alpinelinux/abuild-ci image to run the test suite, which
      has all the required dependencies already installed.
    • Natanael Copa's avatar
      abuild: make sure to not get colors in git_last_commit · 1c00caad
      Natanael Copa authored
      git log may return color codes if users colored output forcibly enabled
      	ui = always
      Use `git rev-list` instead of `git log` to make sure that we don't get
      any color codes.
      fixes alpine/abuild#10042
    • Natanael Copa's avatar
      tests: enable colors in git config · 3d9918f1
      Natanael Copa authored
      Force colors in git config so we can test that we don't get color codes
      in our last commit.
      ref alpine/abuild#10042
  5. 27 Sep, 2021 2 commits
  6. 21 Sep, 2021 3 commits
  7. 20 Sep, 2021 1 commit
  8. 10 Jun, 2021 8 commits
  9. 14 May, 2021 3 commits
  10. 06 May, 2021 2 commits
    • Leo's avatar
      tests(abuild): test whether pyX.Y providers work · 2ed215fa
      Leo authored
    • Leo's avatar
      feat(abuild): add support for pyX.Y providers · ac3ee424
      Leo authored
      Now all python packages that install python modules under
      /usr/lib/pythonX.Y/site-packages will have a provider that indicates
      their MAJOR (X) and MINOR (Y) versions.
      pyX maps to the MAJOR version of the package, its objective is to allow
      users to quickly install a python module without having to search around
      for the correct package, doing `apk add py3.9:foo` will install whatever
      packages provides the foo module.
      The directories checked only go one level deep, so
      '/usr/lib/python3.9/site-packages/date' will generate
      files ending with .py also count and are added with their .py prefix
      stripped away. so '/usr/lib/python3.9/site-packages/six.py' will
      generate py3:six=$pkgver-r$pkgrel.
      The reason for doing this is the same as creating pc:, so: and cmd:, it
      is more reliable and robust to depened on what we known of what the package
      provides than to try to guess via the pkgname.
      Co-authored-by: Chloe Kudryavtsev's avatarChloe Kudryavtsev <toast@toast.cafe>