![\"dev](\"https:\/\/devclouds.io\/blog\/wp-content\/uploads\/2023\/01\/Screenshot_2-4-1024x446.jpg\")
<\/figure>\n<\/div>\n\n\nlet’s go ahead and create a Jenkinsfile in dev branch. Let’s go to dev.<\/p>\n\n\n\n
![\"dev](\"https:\/\/devclouds.io\/blog\/wp-content\/uploads\/2023\/01\/Screenshot_3-3-1024x415.jpg\")
<\/figure>\n<\/div>\n\n\nAnd I’m gonna create a new file.<\/p>\n\n\n\n
![\"basic](\"https:\/\/devclouds.io\/blog\/wp-content\/uploads\/2023\/01\/Screenshot_4-3-1024x503.jpg\")
<\/figure>\n<\/div>\n\n\nThis is the most basic Jenkins file that basically does nothing. But this is the basic syntax we’re going to go through a Jenkins file syntax in more detail in a later section. But here I’m gonna explain you the required attributes for Jenkinsfile in jenkins pipeline.<\/p>\n\n\n\n
Pipeline Syntax: Scripted vs. Declarative<\/h2>\n\n\n\n<\/div>\n\n\n\n![\"Pipeline](\"https:\/\/devclouds.io\/blog\/wp-content\/uploads\/2023\/01\/Screenshot_5-4-1024x412.jpg\")
<\/figure>\n<\/div>\n\n\n<\/div>\n\n\n\nSo the first thing is that Jenkinsfile can be written as a scripted pipeline or a declarative pipeline. So the scripted pipeline was the first syntax of Jenkins file. What it is it allows to write the whole configuration of the Jenkins file using groovy script.<\/p>\n\n\n\n
<\/div>\n\n\n\n![\"groovy](\"https:\/\/devclouds.io\/blog\/wp-content\/uploads\/2023\/01\/Screenshot_6-6-1024x575.jpg\")
<\/figure>\n<\/div>\n\n\n<\/div>\n\n\n\n So the only structure that you have there inside of this is groovy scripts. And you can write the whole configuration here in a flexible manner.<\/p>\n\n\n\n
So there is no predefined structure there however for people who didn’t know or doesn’t know groovy syntax. Or who hasn’t worked with groovy is little bit difficult to start with.<\/p>\n\n\n\n
<\/div>\n\n\n\n![\"pipeline](\"https:\/\/devclouds.io\/blog\/wp-content\/uploads\/2023\/01\/Screenshot_7-7-1024x575.jpg\")
<\/figure>\n<\/div>\n\n\n<\/div>\n\n\n\nThat’s why as a recent addition they actually edit declarative pipeline syntax from Jenkins file. Which is easier to get started with it. Of course it’s not as powerful as the scripted pipeline. Because here you’re not limited in. Anyway but it’s easier to get started with because you have a predefined structure. So this what you see here is basically pre given structure that you have to follow.<\/p>\n\n\n\n
<\/div>\n\n\n\n![\"Required](\"https:\/\/devclouds.io\/blog\/wp-content\/uploads\/2023\/01\/Screenshot_8-6-1024x584.jpg\")
<\/figure>\n<\/div>\n\n\n<\/div>\n\n\n\nIn a declarative pipeline you declare that you are writing a pipeline. And “agent any” basically means that this build is gonna run on any available Jenkins agent. And agent can be a note it could be executors on that note whatever. This is more relevant when you have a Jenkins cluster so to say with master and slaves where you have Windows nodes and Linux nodes etc.<\/p>\n\n\n\n
Basic Syntax<\/h2>\n\n\n\n<\/div>\n\n\n\n![\"basic](\"https:\/\/devclouds.io\/blog\/wp-content\/uploads\/2023\/01\/Screenshot_9-4.jpg\")
<\/figure>\n<\/div>\n\n\n<\/div>\n\n\n\nBut here for the beginning for base we just say “agent any”. So we’ll just run with the next available agent and as I said these two are equivalent to this one here. And they are required attributes you always have to use them. The next required attribute is “stages”.<\/p>\n\n\n\n
And this is where the whole work actually happens so you have different stages of that pipeline. Inside the stages you define stage name and you can define as many stages as you want. Usually you have something like this so you have a build stage. Maybe you have a test stage and then you have a deploy stage like picture above.<\/p>\n\n\n\n
As you see inside the stage you have the steps and here goes the script that actually executes some comment on the Jenkins server or Jenkins agent.<\/p>\n\n\n\n
For example if you’re building a JavaScript application all the NPM install NPM build etc scripts will go here like this.<\/p>\n\n\n\n
If you are you know running tests or for Java back-end all the text execution scripts will be here and the deployment script will be here. So right now let’s just write simple echo comments to kind of test this so here we’re gonna say building the application. And here we’re gonna say testing the application and in here we are deploying the application. And this is a Jenkinsfile and this should work.<\/p>\n\n\n\n
<\/figure>\n<\/div>\n\n\nSo the first thing is that Jenkinsfile can be written as a scripted pipeline or a declarative pipeline. So the scripted pipeline was the first syntax of Jenkins file. What it is it allows to write the whole configuration of the Jenkins file using groovy script.<\/p>\n\n\n\n
<\/figure>\n<\/div>\n\n\nSo the only structure that you have there inside of this is groovy scripts. And you can write the whole configuration here in a flexible manner.<\/p>\n\n\n\n
So there is no predefined structure there however for people who didn’t know or doesn’t know groovy syntax. Or who hasn’t worked with groovy is little bit difficult to start with.<\/p>\n\n\n\n
<\/figure>\n<\/div>\n\n\nThat’s why as a recent addition they actually edit declarative pipeline syntax from Jenkins file. Which is easier to get started with it. Of course it’s not as powerful as the scripted pipeline. Because here you’re not limited in. Anyway but it’s easier to get started with because you have a predefined structure. So this what you see here is basically pre given structure that you have to follow.<\/p>\n\n\n\n
<\/figure>\n<\/div>\n\n\nIn a declarative pipeline you declare that you are writing a pipeline. And “agent any” basically means that this build is gonna run on any available Jenkins agent. And agent can be a note it could be executors on that note whatever. This is more relevant when you have a Jenkins cluster so to say with master and slaves where you have Windows nodes and Linux nodes etc.<\/p>\n\n\n\n
Basic Syntax<\/h2>\n\n\n\n<\/div>\n\n\n\n<\/figure>\n<\/div>\n\n\n<\/div>\n\n\n\nBut here for the beginning for base we just say “agent any”. So we’ll just run with the next available agent and as I said these two are equivalent to this one here. And they are required attributes you always have to use them. The next required attribute is “stages”.<\/p>\n\n\n\n
And this is where the whole work actually happens so you have different stages of that pipeline. Inside the stages you define stage name and you can define as many stages as you want. Usually you have something like this so you have a build stage. Maybe you have a test stage and then you have a deploy stage like picture above.<\/p>\n\n\n\n
As you see inside the stage you have the steps and here goes the script that actually executes some comment on the Jenkins server or Jenkins agent.<\/p>\n\n\n\n
For example if you’re building a JavaScript application all the NPM install NPM build etc scripts will go here like this.<\/p>\n\n\n\n
If you are you know running tests or for Java back-end all the text execution scripts will be here and the deployment script will be here. So right now let’s just write simple echo comments to kind of test this so here we’re gonna say building the application. And here we’re gonna say testing the application and in here we are deploying the application. And this is a Jenkinsfile and this should work.<\/p>\n\n\n\n
<\/figure>\n<\/div>\n\n\nBut here for the beginning for base we just say “agent any”. So we’ll just run with the next available agent and as I said these two are equivalent to this one here. And they are required attributes you always have to use them. The next required attribute is “stages”.<\/p>\n\n\n\n
And this is where the whole work actually happens so you have different stages of that pipeline. Inside the stages you define stage name and you can define as many stages as you want. Usually you have something like this so you have a build stage. Maybe you have a test stage and then you have a deploy stage like picture above.<\/p>\n\n\n\n
As you see inside the stage you have the steps and here goes the script that actually executes some comment on the Jenkins server or Jenkins agent.<\/p>\n\n\n\n
For example if you’re building a JavaScript application all the NPM install NPM build etc scripts will go here like this.<\/p>\n\n\n\n
If you are you know running tests or for Java back-end all the text execution scripts will be here and the deployment script will be here. So right now let’s just write simple echo comments to kind of test this so here we’re gonna say building the application. And here we’re gonna say testing the application and in here we are deploying the application. And this is a Jenkinsfile and this should work.<\/p>\n\n\n\n
![\"sample](\"https:\/\/devclouds.io\/blog\/wp-content\/uploads\/2023\/01\/Screenshot_10-5.jpg\")
<\/figure>\n<\/div>\n\n\n![\"back](\"https:\/\/devclouds.io\/blog\/wp-content\/uploads\/2023\/01\/Screenshot_11-6-1024x497.jpg\")
<\/figure>\n<\/div>\n\n\n![\"jenkinsfile](\"https:\/\/devclouds.io\/blog\/wp-content\/uploads\/2023\/01\/Screenshot_12-5-1024x575.jpg\")
<\/figure>\n<\/div>\n\n\n![\"first](\"https:\/\/devclouds.io\/blog\/wp-content\/uploads\/2023\/01\/Screenshot_13-4-1024x455.jpg\")
<\/figure>\n<\/div>\n\n\n![\"inside](\"https:\/\/devclouds.io\/blog\/wp-content\/uploads\/2023\/01\/Screenshot_14-5-1024x575.jpg\")
<\/figure>\n<\/div>\n\n\n![\"git](\"https:\/\/devclouds.io\/blog\/wp-content\/uploads\/2023\/01\/Screenshot_15-3-1024x548.jpg\")
<\/figure>\n<\/div>\n\n\n![\"build](\"https:\/\/devclouds.io\/blog\/wp-content\/uploads\/2023\/01\/Screenshot_16-5-1024x538.jpg\")
<\/figure>\n<\/div>\n\n\n![\"build](\"https:\/\/devclouds.io\/blog\/wp-content\/uploads\/2023\/01\/Screenshot_17-5-1024x495.jpg\")
<\/figure>\n<\/div>\n\n\n![\"groovy](\"https:\/\/devclouds.io\/blog\/wp-content\/uploads\/2023\/01\/Screenshot_18-6-1024x535.jpg\")
<\/figure>\n<\/div>\n\n\n![\"build](\"https:\/\/devclouds.io\/blog\/wp-content\/uploads\/2023\/01\/Screenshot_19-6-1024x548.jpg\")
<\/figure>\n<\/div>\n\n\n![\"build's](\"https:\/\/devclouds.io\/blog\/wp-content\/uploads\/2023\/01\/Screenshot_20-5-1024x575.jpg\")
<\/figure>\n<\/div>\n\n\n![\"restart](\"https:\/\/devclouds.io\/blog\/wp-content\/uploads\/2023\/01\/Screenshot_21-5-1024x575.jpg\")
<\/figure>\n<\/div>\n\n\n![\"build](\"https:\/\/devclouds.io\/blog\/wp-content\/uploads\/2023\/01\/Screenshot_22-5-1024x561.jpg\")
<\/figure>\n<\/div>\n\n\n