Skip to content
Snippets Groups Projects
  1. Jan 13, 2022
  2. Jun 21, 2021
  3. May 27, 2021
    • Georges Racinet's avatar
      registry-pull-heptapod-push-docker: facility to check consistency · 11c9bbd5
      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.
      11c9bbd5
    • Georges Racinet's avatar
      registry-pull-heptapod-push-docker: basic logging · 240bb4b1
      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.
      240bb4b1
  4. Apr 02, 2021
  5. Mar 20, 2021
  6. Mar 08, 2021
  7. Feb 08, 2021
  8. Dec 15, 2020
  9. Dec 03, 2020
  10. Nov 26, 2020
  11. Oct 07, 2020
    • Georges Racinet's avatar
      Closing default branch · a44e574e
      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
      terminology).
      a44e574e
  12. Oct 03, 2020
    • Georges Racinet's avatar
      build-launch(py3): do not build base image, just retag "partial" · 93d758cc
      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).
      93d758cc
  13. Sep 23, 2020
    • Georges Racinet's avatar
      Using Python 3 and packages (Mercurial) from heptapod/partial image · abdec64b
      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.
      abdec64b
  14. Sep 15, 2020
  15. Sep 22, 2020
  16. Sep 21, 2020
  17. Sep 10, 2020
  18. Sep 08, 2020
    • Georges Racinet's avatar
      build-launch: --no-cache option refreshes base images · adedc243
      Georges Racinet authored
      Now that we rely on the "partial" intermediate image, it's
      vital not to forget to update it, and it makes sense that
      `--no-cache` would force pulling it.
      
      Note that all images pushed to Docker Hub are made with the
      `build-push-main-images` script, that does pass the `--no-cache`
      option.
      adedc243
  19. Sep 07, 2020
    • Georges Racinet's avatar
      Using the partial image produced by Omnibus Heptapod · 3b3c1f2e
      Georges Racinet authored
      This new `heptapod/partial` base image is built like
      `gitlab/gitlab-ce`, but has the Heptapod Rails app instead
      of the upstream Rails app, so we don't need to ADD a tarball
      for the Rails app any more.
      
      As a result, we don't need to specify `heptapod-rails` in
       `heptapod_revisions.json`, not even to keep a record in
      the image, because the detailed info in `/RELEASE` is now
      about Heptapod instead of upstream GitLab.
      
      We still need to write REVISION files because Omnibus Heptapod
      doesn't provide them yet (omnibus-heptapod#8).
      
      The Dockerfile sitting here will keep track in version control of
      the base partial image tag.
      
      Closes #10
      3b3c1f2e
    • Georges Racinet's avatar
      Merged stable into default · 91c09387
      Georges Racinet authored
      Keeping only non version related changes
      91c09387
  20. Sep 04, 2020
Loading