ci_helloworld
ci_helloworld copied to clipboard
gitlab ci runner
Thanks for this great demonstrator.
Have you considered adding an example for the gitlab ci runner? Unfortunately, I don't know if this can be used with a github repository.
We have internally (we actually use Gitlab for our closed source). I would welcome any ideas on how to provide a template for Gitlab in open source.
I don't know a good solution either, but just as a start, you could put the .gitlab-ci.yml
just as an example into this repo even if it doesn't get used (of course it would be kind of schizophrenic if the ci-control file would not be checked by a ci-system).
Let me think about it some more, but in general I agree with the feature request.
A good option would be, to open a fork of this repository on gitlab.com. They support free CI runs for public open source projects. See: https://about.gitlab.com/gitlab-com
@arBmind I just setup an account, so I will play with this and see what I can come up with.
Gitlab now supports running CI pipelines for github projects: https://about.gitlab.com/features/github/. It does come with a catch though: the pipeline won't run for pull requests from forks due to issues with secure variables (https://gitlab.com/gitlab-org/gitlab-ee/issues/5667).
Setting it up is quite easy if you give gitlab access to your account, then it'll do everything automatically. You only have to provide a .gitlab-ci.yml configuration. We are currently using it for Exiv2 to run the pipeline on various Linux distros.
Thats awesome. I have some additional updates on some git work that I have to upstream still, we should include this as well. I'd love to see a PR if your willing to put on together.
Sure, I can prepare something. The question would be however: what do you want to test on gitlab? Probably not the same stuff as on Travis, I guess?
A few options would be:
- run the build in different docker containers (e.g. to test different Linux distros)
- create the doxygen documentation and upload it to gitlab pages
- add a custom runner (allows you to run builds inside vms), but I guess that's too much work (you'd have to host the runner yourself)
I like 1 and 2