Difference between Scripted and Declarative Pipelines

-

Difference between Scripted and Declarative Pipelines


Scripted Pipelines are written in Groovy scripting language, and provide a great degree of flexibility and control over the pipeline's execution. The pipeline definition is written as a script that is executed by the Jenkins Pipeline plugin. It allows the use of imperative programming constructs, such as loops and conditions, which makes it easy to define complex logic.

On the other hand, Declarative Pipelines provide a simpler and more structured way to define pipelines. They are defined using a declarative syntax, which is a set of predefined keywords and constructs that describe the pipeline's steps and stages. The declarative syntax is easier to read and understand, and promotes best practices such as defining stages, post-build actions, and error handling.

Some differences between Scripted and Declarative Pipelines are:

  • Syntax: Scripted Pipelines use a scripting syntax while Declarative Pipelines use a declarative syntax.

  • Complexity: Scripted Pipelines allow for complex logic and conditional statements, while Declarative Pipelines are more limited in their functionality but offer a simpler and more structured approach.

  • Readability: Declarative Pipelines are easier to read and understand, making it easier for teams to collaborate on the pipeline definition.

  • Flexibility: Scripted Pipelines offer more flexibility and control over the pipeline's execution, while Declarative Pipelines are more opinionated and enforce best practices.

In summary, Scripted Pipelines are best suited for complex pipelines that require a high degree of flexibility and control over the pipeline's execution, while Declarative Pipelines are better suited for simpler pipelines that follow best practices and have a more structured approach.

Comments

Post a Comment

Popular posts from this blog

Install Ansible on Ubuntu | How to setup Ansible on Ubuntu 22.0.4 | Ansible install on Ubuntu

-
Image
Ansible is #1 configuration management tool. It can also be used for  infrastructure   provisioning  as well. or You can use Ansible in combination of Terraform which can take care of infra automation and Ansible can do  configuration  management.   Ansible Architecture:   The best way to install Ansible for Ubuntu is to add the project's PPA (personal package archive) to your system. You also would need Boto framework for provisioning resources in AWS cloud. Pre-requisites Create new Ubuntu EC2 instance for installing Ansible, just open port 22. Change Host Name to AnsibleMgmtNode sudo hostnamectl set-hostname  AnsibleMgmtNode Update Repository sudo apt-get update Install Ansible: sudo apt install ansible sudo apt install python3-pip -y  ( this is just comment -  Package manager for python) Install Boto Framework - AWS SDK sudo pip3 install boto boto3 Ansible will access AWS resources using boto SDK. sudo apt-get install python3-boto -y pip list boto | grep boto (the above command
Read more

Installing SonarQube using Docker || Installing SonarQube using Docker on Ubuntu 22.0.4 || Installing SonarQube using Docker-Compose

-
Image
  How to setup SonarQube using Docker compose? SonarQube is static code analyis tool. It is open source and Java based tool. SonarQube can be setup using Docker Compose with less manual steps. What is Docker Compose? Compose is a tool for defining and running multi-container Docker applications. With Compose, you use a YAML file to configure your application’s services. Then, with a single command, you create and start all the services from your configuration.  Since Docker Compose lets you configure related containers in a single YAML file, you get the same Infrastructure-as-Code abilities as Kubernetes. But they come in a simpler system that’s more suited to smaller applications that don’t need Kubernetes’ resiliency and scaling.   The purpose of  docker - compose  is to function as  docker  cli but to  issue multiple commands much more quickly. To make use of  docker - compose , you  need  to encode the commands you were running before into a  docker - compose . yml  file   Run  do
Read more

Setup build agent/slave VM and Integrate with Jenkins Master

-
Image
Jenkins has powerful feature of master slave architecture which enables distributed builds. This article we will learn how to establish slave nodes on Ubuntu machines and integrate with Jenkins Master. Jenkins Master Your main Jenkins server is the Master. The Master’s job is to handle: Scheduling build jobs. Dispatching builds to the slaves for the actual execution. Monitor the slaves (possibly taking them online and offline as required). Recording and presenting the build results. A Master instance of Jenkins can also execute build jobs directly. Jenkins Slave A Slave is a Java executable that runs on a remote machine. Following are the characteristics of Jenkins Slaves: It hears requests from the Jenkins Master instance. Slaves can run on a variety of operating systems. The job of a Slave is to do as they are told to, which involves executing build jobs dispatched by the Master. You can configure a project to always run on a particular Slave machine, or a particular type of Slave ma
Read more