The scope of this issue is for the team to familiarize with https://gitlab.com/gitlab-com/gl-infra/common-template-copier and https://gitlab.com/gitlab-com/gl-infra/common-ci-tasks while creating the first hooks to onboard a new project. ### Objective 1 - GitLab Release Platform Scaffold for the common-ci-tasks We want to add an includable CI component in https://gitlab.com/gitlab-com/gl-infra/common-ci-tasks/-/tree/main/templates that represents the entrypoint in the GitLab Release Platform. Given that [the standard-build componenet](https://gitlab.com/gitlab-com/gl-infra/common-ci-tasks/-/blob/main/templates/standard-build/template.yml) already includes a lot of usefull jobs, we can limit this effort to a simple placeholder job to test the functionality. A good example could be a fake manual "publish" job that only shows up on tag pipelines after the [semantic_release job](https://gitlab.com/gitlab-com/gl-infra/common-ci-tasks/-/blob/main/internal/semantic-release/vault.yml) ### Objective 2 - copier-template integration During the execution of `copier` it will ask the user a [few questions](https://gitlab.com/gitlab-com/gl-infra/common-template-copier/-/blob/main/copier.yml?ref_type=heads#L236), we want to ask an additional one "Do this project use the GitLab Release Platform" and based on that add a the custom component from objective 1 in [the generated `.gitlab-ci.yml`](https://gitlab.com/gitlab-com/gl-infra/common-template-copier/-/blob/main/.gitlab-ci.yml.jinja) https://copier.readthedocs.io/en/stable/ supports cloning the template for a branch by using `--vcs-ref <my_branch>`, so this can be explored by working on branches and bootstrapping projects with ```bash copier copy --overwrite --trust \ --vcs-ref <my_branch> \ gl:gitlab-com/gl-infra/common-template-copier.git \ <my_project> ```