Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • heptapod heptapod
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 190
    • Issues 190
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

April 05-07 - Mercurial Paris Conference 2023 - One day of workshop dedicated to Heptapod and Mercurial usage and workflow. There are still places available for both workshops and talks!

  • heptapodheptapod
  • heptapodheptapod
  • Issues
  • #573
Closed
Open
Issue created Nov 08, 2021 by Georges Racinet@gracinet🦑Owner32 of 32 checklist items completed32/32 checklist items

Shift Heptapod 0.25 to the oldstable series

This will allow in turn to shift Heptapod 0.26 to the stable series.

Description

Bumped series: oldstable Shifted series: stable

Merging

Most tasks The goal is to merge the shifted branch into the bumped branch.

CI Images

  • heptapod-base
    • merge, check/fix assets/install_pythonlibs
    • commit, push
    • pipeline ok
  • heptapod-gitaly
    • merge, commit, push
    • pipeline ok
  • mercurial/hg-current
    • merge, check Mercurial version as expected in kaniko.sh for HG_VERSION==current.
    • merge, commit, push
    • pipeline ok (check resulting Mercurial version)

Components that are forked from upstream GitLab

For these ones, the mapping from series to branch names is:

default: heptapod
stable: heptapod-stable
oldstable: heptapod-oldstable
  • Heptapod Shell
    • merge, commit, push
    • pipeline ok
  • Heptapod Rails:
    • merge, don't commit
    • Important check general base image in heptapod-ci.yml, it should match the bumped series. Release scripts will read this to know for which series they are working. A wrong value hear gives rise to wildly inconsistent binary builds (Omnibus etc.).
    • check cache keys in heptapod-ci.yml. Should be consistent with the relevant Heptapod and GitLab versions in the bumped branch
    • commit in a topic, push, open MR
    • pipeline ok

Python components

  • py-heptapod
    • merge, commit, push
    • pipeline ok (check it's been running on the expected "current" Mercurial version for the bumped branch)
  • HGitaly
    • merge, check that the heptapod-gitaly image is as expected for the bumped branch in .gitlab-ci.yml
    • commit, push
    • pipeline ok

Development, build and release tooling

  • heptapod-tests:

    • merge and check the base image name in .gitlab-ci.yml: it should be the target Heptapod version, e.g, 0-21-testing.
    • commit, push, create a pipeline and watch it use the appropriate image. If the bumped series is stable, the test jobs will fail because the image doesn't exist yet. No use for a MR because of this.
  • HDK: update the release-stable or release-oldstable entry in lib/gdk/config.rb on the heptapod branch (we have one single branch to rule all series as of this writing but that can change in face of big future structural changes).

  • Heptapod Rails:

    • merge the bumped branch into the release branch (e.g., 'heptapod-0-21', 'heptapod-0-22' etc). The diff should be almost empty, especially if the shifted branch was fully merged in the release branch.
    • commit/push
    • trigger the tarball job related to previous push on the release branch.
    • in the job log, check that target Omnibus branch for automatic release is the bumped branch of Omnibus, take note of changeset node ID (part of tarball name) and SHA256 of the tarball.
  • Omnibus Heptapod (branch naming is like all forks, heptapod, heptapod-stable etc.)

    • start a topic on the bumped branch, merge the shifted branch, commit
    • create a changeset with
      • HEPTAPOD_VERSION: x.y-NODE where NODE is the node ID just noted (past example 0.21-a99e86a76ee462e720bcb80c7feb080f06bb9b7d)
      • HEPTAPOD_RAILS_SHA256: the SHA256 of the tarball
    • push, create a MR
    • pipeline passes and creates the proper x-y-testing image
    • downstream pipeline in heptapod-tests passes on the created image (addressed by its hash-based tag)
Edited Nov 11, 2021 by Georges Racinet
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking