Jenkinsfile
From Just Solve the File Format Problem
(Difference between revisions)
Dan Tobias (Talk | contribs) (Created page with "{{FormatInfo | name = Jenkinsfile | formattype = electronic | subcat = Development | subcat2 = | subcat3 = | subcat4 = | subcat5 ...") |
Dan Tobias (Talk | contribs) |
||
Line 23: | Line 23: | ||
The format is based on the [[Groovy]] language. | The format is based on the [[Groovy]] language. | ||
+ | |||
+ | The file is intended to be named <code>Jenkinsfile</code> with no extension. Sometimes Windows-based text and code editors give you a hassle when you try to create files without an extension (it seems to come more naturally on Unix-style systems). | ||
== Links == | == Links == | ||
* [https://www.jenkins.io/doc/book/pipeline/jenkinsfile/ Using a Jenkinsfile] | * [https://www.jenkins.io/doc/book/pipeline/jenkinsfile/ Using a Jenkinsfile] |
Revision as of 20:55, 16 August 2022
A Jenkinsfile is used in a source control repository (Git, Github, etc.) when it is intended to be used with the Jenkins build automation system. It tells Jenkins what needs to be done to build, test, and deploy the system represented by the repository.
The format is based on the Groovy language.
The file is intended to be named Jenkinsfile
with no extension. Sometimes Windows-based text and code editors give you a hassle when you try to create files without an extension (it seems to come more naturally on Unix-style systems).