Skip to content
Snippets Groups Projects
  1. Jun 20, 2022
  2. Oct 17, 2021
    • Georges Racinet's avatar
      Merged hgitaly2 branch into default branch · 52cb5e428ac3
      Georges Racinet authored
      This long-running named branch was to carry intrusive changes
      necessary for operation without any auxiliary Git repository.
      
      As of !65, we've reached the point were everything is neatly
      separated and fully optional, depending on choices made by the
      other Heptapod components.
      
      I have checked as thoroughly as possible that using the `hgitaly2`
      branch of py-heptapod didn't break anything (unit/integration tests,
      functional tests).
      52cb5e428ac3
    • Georges Racinet's avatar
      Heptapod CI: run hg default and hg stable for hgitaly2 branch · 7cd174aa67e8
      Georges Racinet authored
      This is to make sure everything is alright before we merge the
      hgitaly2 branch into default.
      
      (to be ignored in the final merge)
      7cd174aa67e8
  3. Oct 11, 2021
  4. May 14, 2021
  5. May 13, 2021
  6. May 12, 2021
  7. Mar 11, 2021
  8. Feb 15, 2021
    • Georges Racinet's avatar
      Heptapod CI: stop triggering HGitaly downstream builds in hgitaly2 branch · 4ecb9e9f318a
      Georges Racinet authored
      We won't need to create a hgitaly2 branch in HGitaly, because the
      changes are mostly new RPC services, and refactors can be made
      safely (especially with native projects still considered experimental).
      
      On the other hand we needed one in py-heptapod because we're impacting
      potentially all Mercurial projects.
      
      No downstream HGitaly pipeline is configured to work on the
      hgitaly2 branch of py-heptapod, so it doesn't make sense to
      trigger anything.
      4ecb9e9f318a
  9. Jan 05, 2021
    • Georges Racinet's avatar
      Fixing triggered HGitaly pipelines · 070adf351bd7
      Georges Racinet authored
      The `BASE_IMAGE_COLLECTION` variable for the pipeling of
      py-heptapod masks the one defined in the pipeline of HGitaly,
      which changed with the introduction of the comparison tests
      with Gitaly.
      
      Decided arbitrarily to have the variables in the py-heptapod
      pipeline as in the HGitaly pipeline. Could have gone the other
      way.
      070adf351bd7
  10. Dec 04, 2020
    • Georges Racinet's avatar
      Heptapod CI: deriving tag of upstream image from hg branch · f82546177c72
      Georges Racinet authored
      This matches changes done in the base mercurial image so that its
      tag is now `default` instead of `latest`.
      
      At this point, the CI configuration of py-heptapod can be the same
      in its `stable` and `default` branches.
      f82546177c72
    • Georges Racinet's avatar
      Heptapod CI: proper base image for stable, and less jobs · 7e8e6205d1bb
      Georges Racinet authored
      We need to use the `stable` tag of the base image for the `hg-current`
      job. Indeed too bad we can't just propagate the hg branch name, maybe it's
      time to do something about (uniformity makes the stable branch mergeable
      into the default branch without fear)
      
      It doesn't make much sense to run the `hg-default` and `hg-stable`
      jobs for the stable branch of py-heptapod, which won't change Mercurial
      versions, unless hg-stable is for the same hg x.y as hg-current (currently
      not the case).
      7e8e6205d1bb
  11. Dec 02, 2020
  12. Nov 21, 2020
  13. Nov 14, 2020
  14. Oct 16, 2020
    • Georges Racinet's avatar
      Heptapod CI: triggering HGitaly build · c1603fffa2fb
      Georges Racinet authored
      Since py-heptapod also serves as a common library for HGitaly,
      it makes sense to check the impact of landed changes on HGitaly.
      
      This will also propagate scheduler or trigger builds. For example
      if there's a rebuild of hg-default, it should trigger the rebuild of
      py-heptapod, which will trigger that of HGitaly. We'll have a
      few redundant buils along the way (hg-current didn't change in that
      example), but that's tolerable for the time being and could probably
      be further optimized.
      c1603fffa2fb
    • Georges Racinet's avatar
      Heptapod CI: using DAG to run 'install' job in parallel · d23f2dbb4cfd
      Georges Racinet authored
      The install job is expected now to be slower than the other,
      at least if all Docker images are already downloaded.
      d23f2dbb4cfd
  15. Oct 15, 2020
  16. Jun 17, 2020
  17. May 18, 2020
    • Georges Racinet's avatar
      heptapod-ci: avoid reinstallation of Mercurial · 674b7740d22f
      Georges Racinet authored
      Because Mercurial is loaded through PYTHONPATH, it's not visible
      to pip (even if we'd set PYTHONPATH for the pip command), therefore
      that triggers download/build/install of an unrelated Mercurial
      version.
      674b7740d22f
  18. May 17, 2020
  19. May 18, 2020
  20. May 13, 2020
  21. May 09, 2020
  22. May 08, 2020
  23. Apr 30, 2020
  24. Apr 19, 2020
  25. Apr 23, 2020
  26. Mar 12, 2020
    • Georges Racinet's avatar
      tests: a script to run them all · e80029dbb91a
      Georges Racinet authored
      with the upcoming addition of more pytest options, it becomes somewhat
      necessary to have a single script to avoid duplication in the CI
      config and some pain for developers.
      
      run-all-tests passes all subsequent arguments, allowing to add, e.g.,
      HTML coverage generation options and the like.
      e80029dbb91a
  27. Mar 09, 2020
    • Georges Racinet's avatar
      ci: simplified setup with a predefined image · 89c1842e5782
      Georges Racinet authored
      The tests are fast enough that a separate lint stage is overkill
      (it was mostly to try the stage system).
      
      However, having compatibility onto future Mercurial and Evolve
      versions in a second stage is meaningful: these are quite heavier
      because the dependencies can't be prebuilt, and it doesn't make
      sense to run them if the main tests don't pass.
      
      Install check is also on this second stage, that's again a job
      that's not expected to fail often but is somewhat heavier, without
      the dependencies provided by the `ci-py-heptapod` image
      89c1842e5782
Loading