Transfer dune-docker from gitlab.dune-project.org
Zivgitlab now offers registry, so we should probably do building of the docker images here.
Steps:
-
Talk to ZIVGITLAB admin, make sure policy is compatible with our use of the registry
-> zivgitlab is unsuitable, transfer to @kucher's namespace on dune gitlab instead -
transfer/copy pacxx-docker (@jfahl_01 asked Steffen/Dominic to do that) -
make sure the necessary runners are present, or create them
-> now that there is a hpc2se group, recreate the runners a group runners -
enable registry cleanup -- on dune-project.org this is currently done via a bash registry client registry-cli and a repository "schedules" (which is hidden since cleaning up the tags requires elevated user privileges -- talk to @jfahl_01 to get info about this) -
registry-cli was cloned into the hpc2se namespace and is now used from there. This covers pointing no-longer-needed tags to empty dummy images, so should avoid excessive disk space usage on Dune's registry. -
Set up a schedule as described here #8 (comment 51853) to avoid accumulation of dummy tags.
-
-
pacxx-docker uses registry-cli to mark images for deletion -- if registry-cli was moved to zivgitlab, make pacxx-docker use it from there, if something else was used for cleanup, use that mechanism in pacxx-docker as well -
switch the other projects to use pacxx-docker from hpc2se-namespace -
(!12 (merged), pipeline#38394) pacxx-ci (this project itself) -
(pipeline#38395) pacxx-runtime (PACXX's main code) -
(pipeline#38396) pacxx-samples Sample programs used as the unit tests for PACXX -
(pipeline#38397) pacxx-llvm2 Wrapper for checking out llvm and applying local patches -
(pipeline#38398) pacxx-rv2 Wrapper for checking out the region vectorizer and applying local patches -
(pipeline#38399) pacxx-clang A clone of clang with some local patches -
(pacxx!11 (merged), pipeline#38412) pacxx A meta-repository with scripts for checking out all PACXX-repositories for development or manual deployment. -
(pipeline#20476) pacxx-docker A repository for building docker images for the CI-system and general PACXX use.
-
-
Schedules in projects need do be adopted by someone that is not @jfahl_01 -
pacxx-ci (this project itself) -
(No schedule) pacxx-runtime -
(No schedule) pacxx-samples Sample programs used as the unit tests for PACXX -
(No schedule) pacxx-llvm2 Wrapper for checking out llvm and applying local patches -
(No schedule) pacxx-rv2 Wrapper for checking out the region vectorizer and applying local patches -
(No schedule) pacxx-clang A clone of clang with some local patches -
pacxx A meta-repository with scripts for checking out all [ ] PACXX-repositories for development or manual deployment. -
pacxx-docker A repository for building docker images for the CI-system and general PACXX use.
-
-
Ensure pacxx-projektseminar works
Edited by Dr. Jorrit Fahlke