Closed dabroz closed 6 years ago
@dabroz If this is meant just for your private testing purposes and references your private infrastructure, we would not like to include it. Can you get around that e.g. keep it a one directory up etc. ?
It's not specific to my infrastructure, this can be run on any Gitlab instance. But I understand if you don't want to have 2 different CI setups in a project as I can see this being confusing for future users. I can manage my workflow with rebases.
I wanted to have faster turnaround times for HTTPS tests. On Travis I am limited to 4 concurrent tests, however I have a private Gitlab test farm that can do the job much faster. This is basically a 1:1 port of Travis CI setup to Gitlab.