Read about our upcoming Code of Conduct on this issue

  1. 16 Jan, 2022 5 commits
  2. 13 Jan, 2022 7 commits
  3. 21 Jun, 2021 3 commits
  4. 27 May, 2021 2 commits
    • Georges Racinet's avatar
      registry-pull-heptapod-push-docker: facility to check consistency · 11c9bbd5cb5b
      Georges Racinet authored
      Nowadays, the Docker images are produced by a pipeline with a
      Docker tag based on the Mercurial changeset ID in omnibus-heptapod,
      on top of the `testing` tag. The subsequent heptapod-tests pipeline
      uses the image with the precise changeset ID.
      The new `--verify-hg-tag` resolves the expected changeset ID from
      tag and perform the comparison of images, to make sure that
      the `testing` image is the one the functional tests ran against.
    • Georges Racinet's avatar
      registry-pull-heptapod-push-docker: basic logging · 240bb4b143aa
      Georges Racinet authored
      Nothing was displaying the actual calls to `docker pull`, which
      does not repeat its arguments, only the outcomes.
      Using `logging` makes it clear that it's output from the script,
      not from Docker or any other subprocess.
  5. 02 Apr, 2021 1 commit
  6. 20 Mar, 2021 1 commit
  7. 08 Mar, 2021 3 commits
  8. 08 Feb, 2021 2 commits
  9. 15 Dec, 2020 1 commit
  10. 03 Dec, 2020 1 commit
  11. 26 Nov, 2020 9 commits
  12. 07 Oct, 2020 1 commit
    • Georges Racinet's avatar
      Closing default branch · a44e574ec790
      Georges Racinet authored
      Heptapod Docker images for the future 0.17 version
      will be produced by Omnibus Heptapod, hence this project
      has served us well, but is now done.
      The 0.16 stable images will still be produced by this project,
      hence we keep the stable branch. Once 0.17 will become the new
      stable, this project will be made read-only ("archived" in GitLab
  13. 03 Oct, 2020 1 commit
    • Georges Racinet's avatar
      build-launch(py3): do not build base image, just retag "partial" · 93d758ccf758
      Georges Racinet authored
      This is transitory, so that we can proceed with our build process
      transparently, but basically, at this point, we could generate
      the `testing` and `testing-py3` image directly from Omnibus.
      If we drop Python 2, we can then simply forget about
      heptapod-docker (keeping only the stable branch until
      0.17 is the new stable series).
  14. 23 Sep, 2020 1 commit
    • Georges Racinet's avatar
      Using Python 3 and packages (Mercurial) from heptapod/partial image · abdec64b329f
      Georges Racinet authored
      In the introduction of the Python 3 images (now the default), we
      were careful to make a clear distinction between the installation
      provided by Omnibus and the one for Heptapod (notably Mercurial),
      in order to create interferences that we couldn't solve for lack
      of control over the Omnibus install of Python 3.
      With the introduction of Omnibus Heptapod however, we now have
      full control. This move saves about 60M in the Python 3 image, and
      is a step towards not needing any specific installation in the
      Docker image.
  15. 15 Sep, 2020 1 commit
  16. 22 Sep, 2020 1 commit