New CTA repo hickups
This issue is about listing problems created by the migration to the new CTA repository and possible workarounds.
Loss of pipelines schedules
These were not migrated from the old repo to the new one and are not readable anymore, @jleduc recreated the active ones that were running on previous
master branch on 220729.
Let's see how it goes.
We should ask for a dump of previous schedules to the gitlab admins.
Loss of previous docker images
As the new repo regenerated sha for all history, old commits in the new repo have no docker image in the dev docker registry. These images are generated by gitlab CI and gitlab can only run pipelines on top of a branch.
This means that in order to regenerate docker images for older commits we need to create branch from the commit sha and push it to gitlab.
One CI kubernetes gitlab-runner was missing
ctadev02 was not picking any job from the CI, @jleduc deleted the runnner from the pool and registered it again following the CI page instructions.
It is now back in the pool: pipelines will be consumed 2x faster.