Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Create .gitlab-ci.yml #858
I propose to add this file to use the gitlab-ci.
This file will run the
To work, it needs a specific runner, available here mirrored on github here. Feel free to contribute on framagit, or if you want I can transfer this project on YunoHost organisation. If you have any question on how to configure the runner on a gitlab instance contact me, I'll be happy to help you. For your information I tested it on a Virtualbox running a debian stretch.
To implement this solution, there are many solutions:
I'm opening the discussion.
How to test
Well It's very good to use gitlab-ci, but, I don't know if we agree with migrating to framagit after framasoft told users that they will close registration to most of their services in 1-2 years. Perhaps I'm wrong and it has been discussed (I was not here since 3-4 meetings, so I don't know).
For me ideal would be to mirror manually to framagit and perhaps other hosts and do test on framagit.
However, I don't understand why we couldn't have automatic CI test on PR with this solution ?
I didn't know that framagit was concerned about that. In that case we must discuss on which instance we want to move.
To have a proper solution, well integrated to GitHub, which trigger automatically tests and displayed on the PR like this for example (look CI in the PR), we need the paid version of gitlab mirror (free until march), I don't know exactly how to test PR from a fork with the solution base on a manual mirror.
Maybe another option would be to have our own gitlab + gitlab-runner. In that case we would not framasoft mirroring limitation.
For example, yunohost repo stays at github.