[immibis2]

A GUI that lists all the available options is much more user-friendly than a YAML configuration file where you have to guess them or pore over documentation before starting, but even Jenkinsfile syntax looks better than YAML, and Groovy is a real (edit: realer) language that, in theory, can have things like syntax highlighting and auto-completion.

[yepyoukno]

Ugh!

I knew someone would try to say groovy was a real language.

I miss the good old days with bash scripts and cron.

Why must so many diverging environments and tools mingle in our mental space.

[hiAndrewQuinn]

You can always just split the difference and call your shell script with

    sh "./whatever.sh"`

if you want in a modern Jenkinsfile. It's really not that big of a deal to avoid Groovy if you truly cannot stand it.

As for cron, that's also supported out of the box.

    triggers {
            cron('0 0 * * *')
        }

At that point Jenkins is mostly acting as a nice frontend to all those cronjobs and shell scripts, but at least it keeps records of all the logs etc.

[tomkarho]

It's all fun and shells until you start adding parameters especially when those parameters have quotemarks in them. Groovy can get pretty wild with the syntax.

[yepyoukno]

Oh brother don’t think I don’t know how to “work around” anyone else’s favorite tool.

I guess I should be happy it isn’t CA Unicenter.

[hiAndrewQuinn]

See it how you wish; but shell script execution was part of Jenkins from day 1, to my knowledge, over 20 years ago now. It's a 'workaround' the same way walking upstairs is a workaround for an escalator, imo.

[yepyoukno]

Oh I know it! I was slighting Groovy when the old fashion way always worked just fine!

Didn’t mean to draw it out as “one of those” battles.

Cheers!