# tezos-ci and OCaml 5 ### 31-05-2022 Attendees: - Alpha - Lucas - Sudha link: https://tezos.ci.dev/ * The aim of tezos-ci is to replicate gitlab-ci to ocurrent-ci. * tezos-ci use default gitlab repository right now * possibility to use github repository ## base images * upgrade base images dockerfiles to match with the gitlab-ci * the pipeline doesn't change lot * environment config file (RUN) can't change the environment ## Next steps * Bug fixing in the current workflow * closed PRs are also active in the pipeline * manually keeping up with changes in the gitlab CI configuration * build "base images" (tezos-opam-repository@trunk; opam-repository; opam-alpha-repository) * Add built images to a local registry. * Pull the docker image built by ocurrent in the pipeline. Right now it only builds the docker image to validate the build process works fine and doesn't consume the one built by ocluster. * Add multicore/tezos github repo to the pipeline. * Adapt runner in Docker to ocurrent * address the difference in semantics -- Gitlab runner is not the same as ocurrent (Docker/obuilder): gitlab preserves environment variable updates between steps * fix: update .bashrc to reflect env assumptions made in the gitlab CI * Apply a multicore patch on top of tezos/tezos `master` branch to stay on top of the development brach.