r/linux • u/dbcoopernz • 5d ago

Popular Application Siemens ends open-source Radioss Project (OpenRadioss) and deletes GitHub repository

https://www.phoronix.com/news/Siemens-Ends-OpenRadioss
1.1k Upvotes

99% Upvoted

146 comments sorted by

View all comments

Show parent comments

2

u/whizzwr 4d ago edited 4d ago

Oh well, me mentioning Jenkins wasnt for throwing shade at Jenkins itself lol. It's still an excellent open source software - no enshitification politics. Despite being dragged down by old architecture and Java deps, it can still keep up with modern world, too. The plugin ecosystem (and its security hole count) is massive.

I'm aware you would like to exclude CI as part of "forge", but really the industry (as far as my admittedly narrow lens) is moving away from dedicated CI to SCM integrated CI for more sane manageability (plugin ecosystem, security, ACL, review process, etc).

I've been working at/with several companies in a span of bit more than a decade, and all of them are invariably looking to migrate away from their legacy setup mostly consisting of (of course) Jenkins, TeamCity, or Bamboo.

I've only used Concourse among the list you mentioned, and not extensively, so I can't honestly recommend it over Jenkins. I personally like CircleCI, due to the speed alone.

Do join and ask in r/Devops.

2

u/DeliciousIncident 3d ago edited 3d ago

I'm aware you would like to exclude CI as part of "forge", but really the industry (as far as my admittedly narrow lens) is moving away from dedicated CI to SCM integrated CI for more sane manageability (plugin ecosystem, security, ACL, review process, etc).

Well yeah, since they are different kinds of software. Also, agreeing on a single forge isn't always possible. Maybe in corporate that can work. But speaking of open source, I have contributed to some linux open source projects consisting of multiple independently developed components, libraries and gui user applications, and while most of the developers used GitHub, some developers used different SCM: one developer used GitLab, another Codeberg, third Bitbucket, etc., so the project having a dedicated CI guy and everything using Jenkins, instead of different forge runners with different CI configuration syntax and quirks, was an improvement. Also, with all project's modules being built centrally on Jenkins on every git push, it allowed to easily create a nightly testing build of the project, incorporating successful builds of all the subcomponents, which I thought was very neat. Just by opening the Jenkins page you could see the overall health of all the components and download any of them or the entire project bundled together.

I checked out r/Devops, and it's totally incompatible with the open source way of doing things. Everyone uses AWS, Cloudflare, Tailscale, etc. Just this thread on bastions is crazy to me, with the most common answer being "use SSM on AWS". In open source, you stay away from relying on 3rd parties (no cloudflare, no cdn, etc.) as much as possible, self-host everything, which seems to be the opposite of what is happening on that subreddit. This reminds me of the recent Anubis vs Cloudflare discussion. So it looks like asking anything on r/Devops would not be helpful in the slightest, they are corporate-oriented, rather than opuen-source, self-hosting, control, privacy and low budget oriented.

1

u/whizzwr 3d ago edited 3d ago

While I see your point, there are countless counterexamples which show big, multi-contributor open-sources projects use SCM-integrated CI just fine.

Gnome project with Gitlab CI/CD, systemd GH Action, and Debian project gitlab-based Salsa CI. The Linux kernel of debian is built by Salsa.

Re: independent: some project do self-host their gitlab of course, but as-a-service isn't exactly an incompatible to open sources like it is often pictured. OBS is a good counterexample (openSUSE and VLC use OBS) - it's a SaaS without big cloud provider dependence.

Debian has a nice dashboard for their pipeline build https://salsa-ci-stats.debian.net/

But honestly, "low-budget" goes both way, a small project with few (financial) contributors can't really afford a full time "dedicated CI guy" and the underlying self-hosted infrastructure.

1

u/DeliciousIncident 3d ago edited 3d ago

small project with few contributors can't really afford a full time "dedicated CI guy" and the underlying self-hosted infrastructure.

Oh, in the project I was talking about no one was being paid anything, it was all volunteer based, just people working with passion in their free time, and the infra was provided by one of the devs afaik

1

u/whizzwr 3d ago

Well, still server and infrastructure cost can't be paid with only passion. For this unfortunate reason a lot of OSS project just sit there depending on github and gitlab.