Install to-be-continuous on a non-root group in a self-managed GitLab
Starting the Gitlab CI for a project on a self-managed Gitlab, I would like to use the to-be-continuous templates.
So I wanted to follow the dedicated documentation, which requires a public root group to-be-continuous on our Gitlab.
But, for some company purpose, my request for creating this group at the root has been internally refused. As a response, they asked me why the to-be-continuous path isn't variabilized.
How can I workaround this ? Shouldn't it be a good idea to variabilize this path ?
I tried to create a sub_group (non-root) on Gitlab (e.g. mygroup/to-be-continuous) and follow the instructions but giving to the script at https://gitlab.com/to-be-continuous/tools/gitlab-sync/-/raw/master/gitlab-sync.sh the variable DEST_SYNC_PATH=mygroup/to-be-continuous.
The project was well imported, but since the templates references are hard coded, any to-be-continuous internal reference is failing.
E.g. the first pipeline we have to check is the one of Gitlab sync tool, and the first reference is failing :
include:
- project: 'to-be-continuous/docker'
ref: '5.2.2'
file: '/templates/gitlab-ci-docker.yml'Because the docker project reference should be mygroup/to-be-continuous/docker