1. 24 Nov, 2020 2 commits
  2. 14 Nov, 2020 1 commit
  3. 06 Oct, 2020 1 commit
    • Georges Racinet's avatar
      Omnibus: stop hardcoding server-side path to hg · 55b1ee0b3b1b
      Georges Racinet authored
      For server-side operations, we should use the one provided by
      the server, obviously.
      The immediate need is that it varies amongst installation types
      With The new Omnibus packaging method (omnibus-heptapod!3)
      for Heptapod 0.17, it changes from /usr/local/bin (expected to be on PATH)
      to /opt/gitlab/embedded/bin.
      There are several TODOs:
      - read `hg_executable` from config, with remote instances being
        the only exceptions (but these wouldn't call server-side subprocesses
        from the tests).
      - provide a direct helper method on `Heptapod`
      - do the same for Git
  4. 29 Jun, 2020 1 commit
    • Georges Racinet's avatar
      Testing a push with subrepos · 36329a64dac1
      Georges Racinet authored
      On the server side, subrepos should be essentially ignored, at
      least for a push. Since we're in the process of adding server-side
      protections to avoid cloning all subrepos targets and performing
      dangerous commits, it felt necessary to check that basic operation
      is still working.
  5. 11 Jun, 2020 1 commit
  6. 09 Jun, 2020 1 commit
    • Georges Racinet's avatar
      Readthedocs: testing the integration · 8ddce34f7bbd
      Georges Racinet authored
      It's similar to the existing web hooks tests: we're really
      listening to the POSTed data. One reason that is possible
      is that integration/service has a full URL field, instead
      of just project name and id on Read the docs.
  7. 18 May, 2020 1 commit
  8. 29 Apr, 2020 1 commit
  9. 05 May, 2020 1 commit
  10. 29 Mar, 2020 1 commit
  11. 06 Apr, 2020 1 commit
  12. 30 Mar, 2020 1 commit
    • Georges Racinet's avatar
      test for the gate-topics feature of hg-evolve 9.3.0 · aa4d04011cce
      Georges Racinet authored
      It seems that the topic aware client must have hg-evolve 9.3.0 in
      order to push the topic.
      For the time being, besides asserting that clients without the
      `topic` extension don't get topics, we check that the `topic`
      extension *alone* is enough to pull by revision, which is what the
      runners do.
  13. 24 Mar, 2020 1 commit
  14. 14 Mar, 2020 1 commit
    • Georges Racinet's avatar
      project: adapted FS helpers for GitLab 12 · 8036927dba8b
      Georges Racinet authored
      By default, projects are in the hashed path, which is
      derived from the SHA256 of the decimal representation of their
      In `load_tarball` we introduce a new convention that the tarball
      should make two directories, `hg` and `git` that will become
      PATH_TO_PROJECT.hg and PATH_TO_PROJECT.git respectively, and
      update the `issue-3.tar` accordingly.
  15. 13 Mar, 2020 1 commit
    • Georges Racinet's avatar
      topics: added a test for direct publication · 1c1a5dbae996
      Georges Racinet authored
      at the time of our writing, this fails on our current
      GitLab 12 code, because we only prune GitLab branches for
      published topics if there is a corresponding MR.
      as anything related to GitLab post-receive treatment, this
      has to take asynchronicity into account
  16. 29 Mar, 2020 1 commit
    • Georges Racinet's avatar
      Protected branches: removed message test · e3adacf1c0af
      Georges Racinet authored
      In Heptapod 0.8, it's just impossible to trigger
      protected branch errors by Mercurial pushes: we rely on
      Mercurial internal checks for soundness.
      That test may be interesting in the future for Heptapod 0.12 or
      0.13, so we'll push it in a topic against the default branch.
      branch : heptapod-0-8
  17. 19 Feb, 2020 1 commit
    • Georges Racinet's avatar
      Making project names single usage · 14a569275d1c
      Georges Racinet authored
      The various problems with teardown of projects, that can't always
      be fixed remotely, have been a pain for a long time.
      They are worse in constrained environments, as in CI contexts and
      are always a pain point while bumping upstream GitLab versions,
      because we always have to pay the price to make project deletion
      work first.
      By doing this, we lose the ability to easily find the current test
      project in logs etc, but it's comparatively acceptable
  18. 15 Feb, 2020 2 commits
  19. 16 Feb, 2020 1 commit
  20. 15 Feb, 2020 1 commit
  21. 24 Jan, 2020 3 commits
  22. 19 Jan, 2020 1 commit
  23. 15 Jan, 2020 3 commits
  24. 21 Dec, 2019 1 commit
  25. 23 Dec, 2019 2 commits
  26. 02 Dec, 2019 3 commits
  27. 25 Nov, 2019 1 commit
  28. 15 Nov, 2019 1 commit
  29. 18 Nov, 2019 2 commits
  30. 10 Oct, 2019 1 commit
    • Georges Racinet's avatar
      multiple_heads: tests now in a separate module · b92baf11b268
      Georges Racinet authored
      test_push was getting too big, and besides, all tests
      start with pushes. Actually test_push should focus on
      basic operations that can't be more precisely labeled.
      branch : heptapod-0-6-stable