3 ms·
> OSS projects should not have dependencies on non-OSS infrastructure unless they are prepared for this eventuality. I don't think that's the issue. Large part
by progval 6y ago
> OSS projects should not have dependencies on non-OSS infrastructure unless they are prepared for this eventuality.
I don't think that's the issue. Large parts of Travis are open sourc, but no one uses it because they are too complex to set up; and there are better self-hosted solutions than Travis.
Travis was attractive, because it was free hosting, not just software. And worked with just a few clicks
- outsomnia 6y agoIf it's not selfhosted, or it's not FOSS, it's not under your control and can go away any time. It's certainly easy to get into these lassaiz-faire ad-hoc remote free solutions, it's harder to maintain your own CI, but if quality and consistency is important, it's not that hard.