-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gitlab ci runner #4
Comments
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 |
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. |
@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:
|
I like 1 and 2 |
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.
The text was updated successfully, but these errors were encountered: