Pipeline Parameters

Learn the concepts, syntax options, parameter types, and scoping techniques required to define code-driven runtime inputs inside your Jenkinsfile.

What are Pipeline Parameters?

While Phase 2 introduced basic UI-configured job fields, **Pipeline Parameters** in a modern Declarative Jenkinsfile are defined explicitly as code. By declaring a dedicated parameters block at the root layer of your script, you instruct Jenkins to dynamically build its interactive user input dashboard directly from your source control asset.

Code-Driven Parameter Types

A standard declarative configuration supports several specific input types declared directly inside the root block structure:

• The `string` Parameter: A plain text text box ideal for supplying freeform tracking labels, target branch tags, or custom version metadata strings.
• The `choice` Parameter: An explicit multi-option dropdown list layout that prevents input typos by confining user selections to approved safety values.
• The `booleanParam` Parameter: A standard checkbox toggle switch used to pass clean true/false conditional statements to downstream code paths.
• The `text` Parameter: An expanded multi-line string input block reserved for passing longer configurations, scripts, or runtime release summary notes.

Key Concepts

Practical Jenkins Example

The following declarative blueprint introduces native parameter declaration blocks along with programmatic evaluation syntax rules:

pipeline {
    agent any
























    // 1. Defining input configurations natively as code
    parameters {
        string(name: 'GIT_BRANCH', defaultValue: 'main', description: 'Target code branch repository path.')
        choice(name: 'TARGET_ENVIRONMENT', choices: ['Development', 'Staging', 'Production'], description: 'Target deployment infrastructure node.')
        booleanParam(name: 'SKIP_CODE_LINTING', defaultValue: false, description: 'Check box to bypass checking validation stages.')
    }

    stages {
        stage('Initialize Custom Runtime') {
            steps {
                // 2. Reading dynamic arguments using standard string interpolation mappings
                echo "INFO: Initializing build workflows for branch: \${params.GIT_BRANCH}"
                echo "INFO: Target staging server target assigned: \${params.TARGET_ENVIRONMENT}"
            }
        }
        stage('Conditional Quality Controls') {
            steps {
                echo 'INFO: Analyzing step configurations against parameter rules...'
                // Code conditions can evaluate these parameter values directly
            }
        }
    }
}

Practice Exercise: Instantiate a Code-Defined Parameter Matrix