4 pointsby hiAndrewQuinn5 hours ago2 comments
  • immibis25 hours ago
    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.
    • yepyoukno4 hours ago
      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.

      • hiAndrewQuinn4 hours ago
        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.
        • yepyoukno44 minutes ago
          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.

  • pestatijean hour ago
    cant read those snippets... need more contrast