Closed thevikas closed 5 months ago
There are two different ways you could handle this, both documented on the Common Configuration page:
gitlab.project_template = {{xxx}}.{{yyy}}
) or a static name for each service section (gitlab.project_template = xxx.yyy
), this would work.static_fields = project
). Note that this will prevent the project field from being updated (after the initial pull) for all services and I don't believe there's a way to do it on a per-service basis at the moment. However, this is unlikely to be a problem because project fields specifically tend not to change.I'm using project trees in my tasks. So I could use gitlab.project_template = genealogy.backend
?
I cannot use the project name from git pull cause its just "backend"
Have already tried gitlab.project_name
but did not work.
It sounds like gitlab.project_template = genealogy.{{project}}
is what you're after.
My setup has different project codes. How to use that diff project name xxx.yyy? the pull is moving those projects back to orig gitlab project name.