# Master-Slave Architecture:

Master: The Jenkins master is the central server that coordinates and manages the build process. It schedules jobs, monitors agents (slaves), and provides the web interface for users to interact with Jenkins.
Agent (Slave): Jenkins agents (also known as slaves) are worker nodes that execute build jobs dispatched by the master. Agents can be set up on different operating systems and environments to execute builds in parallel.

# Build Jobs:

Jenkins operates based on jobs or tasks known as "build jobs". These jobs define what Jenkins should do, such as fetching source code from a repository, compiling code, running tests, and deploying applications.
Jobs are configured via a web interface or by defining Jenkinsfiles (using Jenkins Pipeline), which are stored in version control systems.

# Plugins:

Jenkins functionality can be extended through plugins. Plugins integrate Jenkins with various tools and services for source code management, build automation, testing, deployment, monitoring, and more.
There are thousands of plugins available in the Jenkins plugin ecosystem, allowing users to customize Jenkins to fit their specific needs.

# Web Interface:

Jenkins provides a user-friendly web interface that allows users to create, configure, and monitor build jobs. Users can view build logs, manage plugins, set up credentials, and view reports and statistics.

# Distributed Builds:

Jenkins supports distributed builds, where different build jobs can be executed on different agents simultaneously. This helps in scaling Jenkins for large projects and optimizing build times.

# Static Agents:

    Static agents are traditional Jenkins agents that are configured and permanently registered with the Jenkins master. They typically run on dedicated hardware or virtual machines (VMs) and are always available to execute build jobs.

# Dynamic Agents:

    Dynamic agents are provisioned on-demand by Jenkins to handle workload spikes or specific job requirements. Jenkins can dynamically spin up instances of these agents in cloud environments (like AWS, Azure, Google Cloud) using plugins such as Amazon EC2 Plugin, Azure VM Agents Plugin, or Google Compute Engine Plugin.


# Permanent vs. Temporary Agents:

Permanent agents are long-lived agents that remain registered with Jenkins indefinitely, available for any job execution. They are typically used for stable environments where consistent availability is required.
Temporary agents are short-lived agents that Jenkins spawns for specific jobs and releases afterward. They are useful for optimizing resource utilization and scaling based on workload demands.

  # Freestyle Project:
    A Freestyle project is the simplest form of Jenkins job. It allows you to configure a series of build steps, which can include shell scripts, batch commands, or other build actions. You have flexibility in defining the sequence and execution of these build steps.

   # Pipeline:
    Jenkins Pipeline is a suite of plugins that supports continuous delivery and automation of tasks in Jenkins. Pipelines can be defined using a DSL (Domain-Specific Language) called Groovy, either in a Jenkinsfile stored within your version control system or directly in the Jenkins UI. Pipelines offer robust capabilities for defining complex workflows, including parallel execution, stages, and advanced conditions.

   # Multi-configuration Project:
    Also known as Matrix projects, these allow you to run the same build job on multiple configurations (such as different operating systems, JDK versions, or browser types) in parallel. It's useful for testing software across different environments simultaneously.

   # GitHub Organization:
    This build type allows Jenkins to automatically create and configure jobs for repositories within a GitHub organization or GitHub Enterprise. It scans GitHub repositories and creates jobs based on predefined templates or configurations.

   # GitHub Pull Request Builder:
    This type of build job is triggered automatically when pull requests are opened or updated on GitHub repositories. Jenkins checks out the pull request, builds it, and reports back the status (success, failure, etc.) on GitHub.

   # Maven Project:
    Jenkins provides specific support for Maven-based projects. Maven projects automatically manage dependencies, perform builds according to Maven lifecycle phases (like compile, test, package), and can publish artifacts to Maven repositories.

   # Freestyle Maven Project:
    Similar to a standard Freestyle project but specifically configured to build Maven-based projects. It integrates Maven commands directly into the build steps.

   # Pipeline (Multibranch):
    This type of pipeline job automatically creates a new Jenkins Pipeline job for each branch in a repository. It scans branches and applies the Pipeline configuration defined in the Jenkinsfile within each branch.The definition of a Jenkins Pipeline is written into a text file (called a Jenkinsfile) which in turn can be committed to a project’s source control repository. This is the foundation of "Pipeline-as-code"; treating the CD pipeline as a part of the application to be versioned and reviewed like any other code.

# Declarative Pipeline Syntax

# Scripted Pipeline Syntax

 # Key Syntax Elements

Pipeline Block: Defines the entire pipeline structure.
Agent: Specifies where the pipeline will execute.
Stages: Divides the pipeline into stages (e.g., build, test, deploy).
Steps: Actions to be executed within each stage (e.g., shell commands).
Environment: Sets environment variables for the pipeline.
Post: Defines actions to be taken after stages (e.g., notifications).
Triggers: Specifies conditions or schedules to trigger the pipeline.
Options: Configures pipeline options (e.g., timeout, retry).