@catonano
You can enable shared runners in your project settings, which means it runs on runners hosted on infrastructure other than yours. In fact it might even be enabled by default iirc.
But can I build a project on Gitlab servers ?
@catonano
It kind of depends on what you want to achieve. You can create a ci configuration to do a build and then do something with that build, e.g. deploy it somewhere. If you set up your repo to use shared runners this will be run on publicly available shared runners rather than having to host your own runner.
@smeagol so publicly available shared runners do exist ?
that's the thing I wanted to know
I just would like my project to be built and the unit tests run, the log collected somewhere
@catonano
Yeah for sure. Log into your repo page in gitlab then settings->ci/cd->runner settings. On the right is a header 'shared runners' and an option to enable. Below that is a list of available runners, one of which the job will be run on. The output will be shown in ci/cd->pipelines as normal. There's some limitations to how much build time you can use each month on private repos.
@catonano
However if you mean can you configure it to do a build and then automatically appear as a 'release' against your repo, I don't believe you can do that. I may be wrong though. Gitlab seem to have a disturbingly fast release schedule and stuff changes all the time.
@catonano This conversation appears to me like you're talking to yourself. The replies are missing.
AFAIK, you can add a Runner to your GitLab CI server provided it has a public IP