Perhaps the phrase "not a huge deal" was ill-advised, apologize for that. Am not sure from the documentation you reference that it's a documentation problem - does it not consistently reference "Jenkinsfile"? Since the default pipeline definition in a pipeline job (with pipeline from SCM) is Jenkinsfile, the documentation seems right to me (from standpoint of documenting reality).
Calling it Jenkinsfile.groovy isn't 100% accurate, since the content of that file isn't idiomatic Groovy. Supports a lot of Groovy-ish constructs, but isn't Groovy proper. Jenkinsfile.pipeline would make sense, as it is a pipeline definition. I understand that a ".pipeline" extension isn't recognized by many tools as a text file construct. Although, most tools would allow you to map extensions as desired. Seems unlikely that the historical name "Jenkinsfile" would be changed. I've been known to create multiple pipeline files in a repository, and to name them with schema "foobar.pipeline". I think that's a preference, and to each their own. -- 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/38102661-6168-4339-b6fc-16f51b9c2e73%40googlegroups.com.
