1. 29 Jun, 2019 1 commit
  2. 26 Jun, 2019 2 commits
  3. 19 Jun, 2019 1 commit
  4. 11 Jun, 2019 1 commit
    • Oliver Smith's avatar
      CI: test_upstream_compat: disable binutils check · cd94b3ef
      Oliver Smith authored
      We need to freeze binutils at 2.31 (Alpine has 2.32 already), until
      issue #295 is resolved. Let's disable the test, so the testsuite passes
      again if everything else is good, and we don't start to ignore whether
      it fails or not.
  5. 30 May, 2019 3 commits
  6. 24 May, 2019 2 commits
  7. 14 Apr, 2019 1 commit
    • Oliver Smith's avatar
      CI: enable crossdirect again · 1031ff82
      Oliver Smith authored
      All bugs should be ironed out now. Let's get some more testing by
      enabling crossdirect in CI again. The crossdirect feature is still only
      in pmbootstrap master, not in the latest pmbootstrap release. But if it
      works without problems for some time, we're ready to make a release.
      This reverts commit 6e3252e4.
  8. 05 Apr, 2019 2 commits
  9. 05 Mar, 2019 1 commit
    • Oliver Smith's avatar
      CI: check_mr_settings.py: fix check for same repo (!255) · 3030c00b
      Oliver Smith authored
      Do not crash when a MR was made from the same repository, because the
      "allow_maintainer_to_push" key does not exist in the GitLab API's
      output. Check first if the "source_project_id" is the same as the
      "target_project_id", and if it is, do not try to access
      "allow_maintainer_to_push" at all.
  10. 28 Feb, 2019 2 commits
    • Oliver Smith's avatar
      CI: check if maintainers can write to MR branch (!248) · e8a7926e
      Oliver Smith authored
      Check if users activated the 'Allow commits from members who can merge
      to the target branch' option in their MRs.
      Add the "only" parameter to each job in .gitlab.yml, so the pipeline
      can properly run in a "merge request specific context" and give us the
      environment variable that contains the MR ID.
    • Oliver Smith's avatar
      CI: add "ci:ignore-count" and "ci:skip-build" (!210) · 94632850
      Oliver Smith authored
      Allow skipping the "too many packages changed" check by specifying
      "ci:ignore-count" in the commit message.
      Allow skipping the package build step by specifying "ci:skip-build"
      in the commit message. In contrary to the usual "skip ci" method,
      this will still run all the other CI checks.
  11. 27 Feb, 2019 1 commit
  12. 15 Feb, 2019 1 commit
  13. 22 Jan, 2019 1 commit
    • Oliver Smith's avatar
      CI: show meaningful error for outdated pmaports (!167) · 158ac151
      Oliver Smith authored
      When we bump the version in pmaports.cfg and the min. required pmaports
      version in the pmbootstrap code, then forks of pmaports.git must be
      rebased on pmaports.git master. Otherwise "pmbootstrap init" fails, and
      because we have it set to quiet (so the output does not distract from
      the interesting output if everything goes fine), there was no meaningful
      error message yet.
      Wrap the "pmbootstrap init" call and display a helpful message that
      tells the user to rebase.
  14. 02 Jan, 2019 1 commit
  15. 30 Dec, 2018 1 commit
    • Oliver Smith's avatar
      test_aports_kde: test Qt version too and rename (!119) · 8d4232d1
      Oliver Smith authored
      Rename test_aports_kde.py to test_aports_framework_versions.py and
      generalize all referenes in the code from "KDE frameworks" to
      "frameworks". Check that all Qt packages have the same version, support
      having the real version in _pkgver and pkgver=9999.
      Scan all pmaports, not only the ones in the kde dir. Do not output all
      packages of the "other" category anymore, the package count is enough.
  16. 17 Dec, 2018 1 commit
  17. 13 Dec, 2018 3 commits
    • Oliver Smith's avatar
      build_changed_aports: allow existing remote · 6179f457
      Oliver Smith authored
      In this CI test, we add the upstrem postmarketOS/pmaports.git
      remote to the checked out git repository. Do not crash when it exists
      already, so we don't need to remove it before each run when testing
    • Oliver Smith's avatar
      build_changed_aports: don't build deleted aports · 683bc62f
      Oliver Smith authored
      Do not attempt to build deleted aports and fail on them. In the
      overview of changed files, note which ones have been deleted.
    • Oliver Smith's avatar
      Cosmetic: build_changed_aports: improve comments · c7b42e9e
      Oliver Smith authored
      * Move a comment that was after a line of code above that line. That
        line was very long compared to all others in the file, and now the
        file fits in 80 characters in every line, like PEP-8 recommends.
      * Replace "folder" with "dir" in the comments (as I learned lately
        that "folder" is only a Windows concept).
  18. 29 Nov, 2018 1 commit
  19. 27 Nov, 2018 1 commit
  20. 26 Sep, 2018 1 commit
  21. 25 Sep, 2018 1 commit
  22. 22 Sep, 2018 1 commit
    • Oliver Smith's avatar
      Remove obsolete test case test_aportgen.py · e9fd5099
      Oliver Smith authored
      This test case only makes sense in the pmbootstrap repository, and
      we have it there already. In pmaports, we don't need to check if the
      "aportgen" code is working - and to check the versions of the aports
      we already have the test_upstream_compatibility case.
  23. 05 Sep, 2018 1 commit
  24. 04 Sep, 2018 1 commit
    • Oliver Smith's avatar
      Add test cases and .gitignore · 0d5e2fae
      Oliver Smith authored
      Copy all test cases from the pmbootstrap repository, that are actually
      testing the aports. They were all adjusted to work nicely in this
      repository, together with a brand new set of gitlab-ci configs.
      This also includes the changes from this merge request, that had a
      better detection of changed packages: