Using external scripts is generally the preferred way of doing things anyway, so you are going the correct route. Writing scripts that reside in your SCM and then orchestrating them with a Jenkinsfile is the recommended way. As for the filename, most editors that I know of have a way to associating a filename with a language, I do this in VSCode to associate Jenkinsfile with groovy handling and it works just fine.
On Thu, May 14, 2020 at 1:20 PM Jérôme Godbout <[email protected]> wrote: > Probably because only one OS (read Windows here) only rely on extension to > open file. The shebang is enough on most system. Pipeline Groovy is not > pure groovy, the script into pipeline is a Frankenstein of Groovy and > Jenkins features. Like some other point out, it should have been .pipeline > or .jenkins or something like that. Really wish they went standard on this > one, it make horrible scripts that aren’t reusable anywhere else. I mostly > just call python script and gave up on the NON CPS and weird loop behavior, > did anyone said script approval madness??? At least my python script can be > reuse without the need of the Jenkins special env. Some would say this is a > security breach, but I prefer having secure repository and Jenkins server, > not the execution of the script per say, it’s grail run to try to secure > from code execution like that, it will never be good, it just an annoyance. > Wish there was a fork without that script approval and no CPS. Let me > secure the source of my Jenkins scripts (certificate and private key ok) > and assume my dev know what they do, it’s not like they cannot access the > code anyway. > > > > > > *From:* [email protected] <[email protected]> > *On Behalf Of *Kris Z > *Sent:* May 14, 2020 10:00 AM > *To:* Jenkins Users <[email protected]> > *Subject:* Jenkinsfile naming convention > > > > Hello, > > > > I was reading the documentation for Jenkins User Handbook ( > https://www.jenkins.io/doc/book/getting-started/), specifically the > section on Pipeline and creating the Jenkins file. > > > > My specific question is, why isn't the Jenkinsfile named > Jenkinsfile.groovy? > > > > When adding the extension all the operating systems have tools to open a > file with editor and they launch syntax highlighting. > > > > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/df168746-6d8e-443c-9279-436eb6f5c58f%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/df168746-6d8e-443c-9279-436eb6f5c58f%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/YQBPR0101MB1074F340F78163CEC95CF968CDBC0%40YQBPR0101MB1074.CANPRD01.PROD.OUTLOOK.COM > <https://groups.google.com/d/msgid/jenkinsci-users/YQBPR0101MB1074F340F78163CEC95CF968CDBC0%40YQBPR0101MB1074.CANPRD01.PROD.OUTLOOK.COM?utm_medium=email&utm_source=footer> > . > -- Website: http://earl-of-code.com -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVdPfOXF9axcw8T0y5SDrqU%2B5iohNUjyiUsD2X0vowkHhA%40mail.gmail.com.
