Hi Roger, Thanks for working on that.
The other downside is that these systems are libtiff group runners; they are only accessible to members of projects within the libtiff GitLab group, so external or internal contributors who open merge requests from forked repositories won’t have the CI builds run successfully. Only branches pushed to the libtiff repository will run.
That's indeed a major drawback to me. It will be hard to accept contributions from casual contributors with such setup since they won't have push rights to the libtiff repository. Is there somehow a way to have a mix of self-hosted runners for thorough tests, while we keep the existing/past gitlab provided runners for everyone?
Even -- http://www.spatialys.com My software is free, but my time generally not. _______________________________________________ Tiff mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/tiff
