I'm not sure how to define "huge deal". I think it really has to do with
someone not thinking things through when they document on the Jenkins
website: https://www.jenkins.io/doc/pipeline/tour/hello-world/ .
I mean, it's going backwards several decades. As of now, all operating
systems: Linux, Mac, Windows, and others understand the concept of having a
file extension. I use Linux as my default development environment.
Unix-like operating systems have also come as far as adding a shebang to
the top of the file to all files which include source code that is a
scripting language. This concept of using a shebang is very well
understood in Unix-like operating systems.
There are so many scripting languages out there, how could I tell what
language is being used within a Jenkinsfile? I mean it is using Groovy and
the Jenkins team is not creating a new scripting language. It should be
explicitly indicating that Groovy is being used by the following:
1. Adding a ".groovy" to the "Jenkinsfile" example, so it is
"Jenkinsfile.groovy".
2. Adding a cross-platform compatible shebang to the top of the file:
1. Example source code:
1. #!/usr/bin/env groovy
2. Example screenshot:
[image: test_groovy_example.png]
1.
I scoured other training material and I see people that call themselves
"trainers" (especially on YouTube) and create files that have a ".pipeline"
extension. Which is wrong. If the file is a Groovy scripting language it
should be named "pipeline_x.groovy". This way the development tools on
Linux can automatically perform syntax highlighting and file type assesment.
How could I submit a defect against the documentation to have this looked
at and changed?
--
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/23d00a11-4458-4e72-8e7c-76846b56ce4d%40googlegroups.com.
