The images used by the CI jobs used to be generated in a separate repository (tezos/opam-repository). This milestone aims to bring them inside tezos/tezos.

NOTE: a lot of the work is actually happening in tezos/opam-repository (preliminary simplifications and all) but we cannot assign milestone across repositories.

Motivation

Currently, tezos/opam-repository has two purposes:

• force devs, users and the CI to use the same set of dependencies, with the same versions;
• generate Docker images with those dependencies for the CI.

Having this separate repository makes it significantly harder to update Octez dependencies.

Scope

The technical solution that was chosen to force dependencies is to have tezos/opam-repository be an opam repository that we can tell opam to use instead of the default one. It is complex and it lacks flexibility. We want to replace this with a lock file.

Somewhat orthogonally, we want to move Docker image generation to tezos/tezos directly.

Work Breakdown

Using Opam Lock

• (days) !12029 (merged) Add a script to generate an opam lock file
  • (optional) (???) Find a way to not have utop and its dependencies in the lock file.
• (days, ready for review) !12100 (merged) Have make build-deps and make build-dev-deps use this lock file instead of tezos/opam-repository
• (days, ready for review) opam-repository!500 (merged) and !12345 (merged) Modify tezos/opam-repository to be able to build Docker images from the lock file, ignoring its packages folder
  • (days) Update Dockerfile and scripts
  • (hours) Update the documentation regarding how to update Octez dependencies
  • (minutes) Remove the packages folder from tezos/opam-repository
  • (hours) Remove update_opam_repo.sh from tezos/tezos, and the check that the result of this script an empty patch
• (optional) (hours) Clean up version.sh in tezos/tezos
  • rename full_opam_repository_tag, opam_repository_tag to better reflect their new roles
  • maybe some other variables are no longer needed