Skip to content
Snippets Groups Projects
  1. Apr 05, 2022
    • Georges Racinet's avatar
      hg-git: require version < 1.0 · d4d1761f95ba
      Georges Racinet authored
      The publication of the final 1.0.0 version of hg-git brings
      in a minor incompatibility, that we will address once the
      current default branch becomes the stable branch (heptapod#658).
      
      This is not a problem for shipped versions because the requirements
      specified with the Rails app (both in heptapod and in release branch)
      already pin hg-git to 0.10.x
      d4d1761f95ba
  2. Feb 05, 2022
    • Georges Racinet's avatar
      Stop post-processing branchmap entries for obsolescence · c78aee1fe363
      Georges Racinet authored
      With the Mercurial 6.1 (core see heptapod#633) taking obsolescence
      into account while updating branchmap, it is no longer necessary
      to perform the (very slow) post-processing provided by the evolve
      extension.
      
      Because of the big jump in minimum required Mercurial version,
      we make it a major version change.
      
      Fixing heptapod#632 will thus boil down to requiring
      py-heptapod>=4.0.0dev0
      
      This post-processing was the standard if evolve is activated
      (through the single heads enforcement logic),
      but the heptapod extension was (and still is) disabling it because
      it needs to call it itself anyway.
      See 834eb9379d73 for details.
      c78aee1fe363
  3. Oct 25, 2021
    • Georges Racinet's avatar
      Error handling: ensure tracebacks are produced in GitLab mirror hook · 4728e33a7d5c
      Georges Racinet authored
      Here we consider straight Abort errors to be user errors, hence not
      warranting a server-side traceback in the logs. This can certainly
      be improved further, as it doesn't prevent server-side tracebacks
      to be displayed to SSH clients, for instance.
      
      This makes use of `hg-loggingmod` 0.3.0 ability to log tracebacks in
      the logs.
      4728e33a7d5c
  4. Apr 03, 2021
  5. Apr 02, 2021
  6. Apr 01, 2021
  7. Mar 19, 2021
  8. Feb 23, 2021
    • Georges Racinet's avatar
      Extensions: require and activate config-express · b14b26ff5180
      Georges Racinet authored
      With the given defaults settings, clients won't see any difference.
      
      hg-configexpress 0.4.0 passes all tests with Mercurial 5.6,
      the series we're using in current Heptapod.
      
      The question of how to configure selected projects is entirely open.
      For now, users have to modify the repo (or group) HGRCs on the server
      file system.
      
      Since there are auxiliary files, the question of backuping them is
      also open.
      
      Closes heptapod#190
      b14b26ff5180
  9. Feb 13, 2021
  10. Jan 28, 2021
  11. Jan 10, 2021
  12. Dec 08, 2020
  13. Dec 02, 2020
    • Georges Racinet's avatar
      requirements: adding hg-loggingmod · 1cc143ec5781
      Georges Racinet authored
      The default configuration has been using it for a while.
      Of course in production Heptapod context, that's always provided
      (by the requirements shipping with the Rails app), but it can
      be missing in some development contexts - that is a pain, and
      potentially a waste of time because anything output on stderr
      is considered an error if spawned from Rails.
      1cc143ec5781
  14. Nov 29, 2020
    • Georges Racinet's avatar
      Requiring attrs · cdc11a4d00bc
      Georges Racinet authored
      This made 1.1.2 unusable outside of dev environments.
      
      Thought it was automatically provided because Mercurial uses it.
      Big mistake, Mercurial vendors it. Of course can't be detected by
      a pytest session...
      1.1.3
      cdc11a4d00bc
  15. Nov 21, 2020
  16. Aug 25, 2020
  17. Jun 08, 2020
  18. May 13, 2020
  19. May 09, 2020
  20. May 06, 2020
    • Georges Racinet's avatar
      gitlab-mirror: filtering out obsolete heads in branchmap · 5016d915ae0d
      Georges Racinet authored
      As of hg-evolve 9.3.1, some obsolete heads are ignored in the
      protection agains multiple heads. These happen typically in
      stacked topic scenarios, after amendment of the anterior topic.
      
      These should not count as multiple heads in our exposition to GitLab
      either, we're applying the same function to filter them out.
      
      This has us convert systematically to changeset contexts (standard
      abbrev being `ctx`) whereas we were doing so before only in the loop
      to ignore closed branches.
      5016d915ae0d
  21. Apr 30, 2020
  22. Mar 10, 2020
    • Georges Racinet's avatar
      GitLab hooks: post-receive directly through internal REST API · a9f1a24b9679
      Georges Racinet authored
      This implements the `post-receive` hook by a direct HTTP call to the
      internal API endpoint. For this, two new config parameters in the
      `heptapod` section are introduced:
      
      - gitlab-internal-api-secret-file
      - gitlab-internal-api-url
      
      
      We're keeping the previous structure, with a `name`
      that's now almost useless and leads us to the
      complication of the `_hook_methods` dict.
      This keeps compatibility for the caller (also
      part of this package since Heptapod 0.12), allowing
      us to refactor in a separate step.
      a9f1a24b9679
  23. Apr 23, 2020
  24. Mar 09, 2020
    • Georges Racinet's avatar
      started to rewrap hg-git · 687c6dd60738
      Georges Racinet authored
      This is done by subclassing `GitHandler`, for now
      adding `update_exportable_for_named_branches`, almost
      identically.
      
      The only functional difference is that named branches and
      topics are always exported, i.e., not depending
      on the value of `hg-git.export-named-branches`
      687c6dd60738
  25. Dec 15, 2019
Loading