Re: Jenkinsfile naming convention

Am Donnerstag, den 14.05.2020, 06:59 -0700 schrieb Kris Z: When adding the extension all the operating systems That's not quite true. Unix-like OS' don't need one since they identify files by content, not by extension. So, a proper shebang line at the top should be sufficient to identify your

Re: Jenkinsfile naming convention

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

RE: Jenkinsfile naming convention

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 .

Re: Jenkinsfile naming convention

On Thu, May 14, 2020 at 12:22 PM Kris Z wrote: > 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/ . > > Thanks for your interest. The

Re: Jenkinsfile naming convention

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 Je

Re: Jenkinsfile naming convention

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

Re: Join us for Jenkins Online UI/UX Hackfest on May 25-29!

Thanks Oleg! Also if people can help spread the word via Twitter or any other means that would be greatly appreciated! On Thu, May 14, 2020 at 6:15 PM Oleg Nenashev wrote: > Dear all, > > On behalf of the Jenkins User Experience, Documentation and > Advocacy&Outreach special interest groups, we

Join us for Jenkins Online UI/UX Hackfest on May 25-29!

Dear all, On behalf of the Jenkins User Experience, Documentation and Advocacy&Outreach special interest groups, we are happy to announce the Online UI/UX Hackfest on May 25-29! Everyone is welcome to participate, regardless of their Jenki

Re: Role based strategy - pattern for jobs for example two maps deep

Hello, Nobody has this issue that I can give a role access to a specific map and what the pattern than should be? I must say, we are going in the near future to a new version of Jenkins, but on this moment I'm talking about Jenkins version 2.9! Nico. -- You received this message because you

Re: Jenkinsfile naming convention

I think historical convention. It's not a huge deal, you can use any file name you want, if you set your pipeline job up to use your path/filename instead of the default. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from th

Pipeline SCM trigger breaks

Hi, I have configured a multibranch pipeline (declarative), which checks out several git repositories and has pollSCM('') configured: I deleted and recreated the build for branch 'int'. The first two builds were triggered by branch indexing and manually by me. The 'Git Polling Log' from yesterd

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 a