The whole point we started using automation servers as an integration point was to avoid the "it works on my machine" drama. (Have watched at least 5 seasons of it - they were all painful!).
+1 on running the test harness locally though (where feasible) before triggering the CI server.
So, if I understand correctly, you’re not so much concerned about the p2p architecture, rather than the default seeding policy? (You’d prefer that to be selective rather than open by default? )
But seriously, it would be nice to distribute it. We already have other options coming slowly. The fediverse forges are being worked on and should be available in 2025, like https://forgejo.org/
Probably not the "easiest", and it's not really production-ready yet, *but* it is the one open source solution for hosting open source software that will never be affected by the "Explores Sale" problem - the same way that BitTorrents have never had that problem: it is a fully decentralized, peer-to-peer network for hosting source code.
agreed. Jenkins has suffered from a lot of problems - plugin maintenance across version upgrades being key - but it has also overcome a lot of these problems. It gets criticism just for being... "old". But it is an automation server that is as battle-tested as they come!
Also, being old gives it a huge advantage: you can bet you won't need a major rewrite of your pipelines in a couple of years when e.g. GitLab sells, or Microsoft decides GH actions aren't so free (or fast) any more, etc.
I have to say "Datadog" isn't exactly as scary as "Microsoft" was, back when it bought GitHub.
Ok, they didn't kill the open source community which is what we feared at the time (because they found a way to make more money from it), but I'm still more skeptical of Microsoft essentially controlling the world's open source software than Datadog buying an open core company.
But with Microsoft now painting everything with its "AI" brush, aren't you, as open source maintainers, concerned about keeping the world's FOSS on a proprietary platform?
> The risk only comes in if gitlabknockoff was AWS, Azure, or GCP, which we're still learning what to do about.
Exactly! It really makes me wonder how GitLab thinks Datadog can help them defend against this risk. Then again, they're not open source - just open core.
- finding what the domain name is ?
- resolving the DNS to an IP address ?
Radicle solves both problems in theory, but more the latter than the former right now:
- there is some basic functionality to search for projects hosted on Radicle, to find the right repo id (I expect this area will see a lot more activity and improvements in the near future),
- given a repo id, actually getting the code onto your laptop. This is where the p2p network comes in, so that the person hosting it doesn't always need to keep their computer/router/tv box on, etc.
And I know one more of those people already!
5 more to go.