GitHub Actions Are a Problem

Re:GitHub Actions Are a Problem by marcosdumay on Sunday November 12, 2023 @11:54AM (#38241865)

Building Java and C# on the command line nowadays is a hard undertaking, requiring weeks of learning and debugging, just to have your code change in a way that makes the scripts outdated at any time (oh, and it's never portable).

I really don't get why people use those complex CI/CD tools for other languages, but at least on the enterprise ones, I can understand people moving from the IDE into some huge centralized mess that can import it.

[ Parent | on HN ]

Re:GitHub Actions Are a Problem by twic on Sunday November 12, 2023 @12:23PM (#38242182)

Why does Java take weeks?

For a straightforward application or library project, you can fill in this form and get a shovel-ready build: https://gradle-initializr.cleverapps.io/

I usually tweak it a bit, but that's minutes, not weeks.

There's often more stuff to add as a project grows, but again, minutes to hours for the common stuff. Setting up publishing to a Maven repository is more work than I'd like, but it's still not weeks.

So what are you doing that it takes so long? And how long would that take if done any other way?

[ Parent | on HN ]

Re:GitHub Actions Are a Problem by neonsunset on Sunday November 12, 2023 @11:56AM (#38241901)

Building C# is quite literally 'dotnet build -c release'.

[ Parent | on HN ]

Re:GitHub Actions Are a Problem by Kwpolska on Sunday November 12, 2023 @12:19PM (#38242142)

(And building code that targets the classic .NET Framework can usually be accomplished by a single call to msbuild.exe.)

[ Parent | on HN ]

Re:GitHub Actions Are a Problem by hypeatei on Sunday November 12, 2023 @12:08PM (#38242029)

Exactly. I don't know where the newer .NET versions get the bad rap from.

You can criticize Microsoft for other things but .NET is not one of them. They've done a great job with it.

[ Parent | on HN ]