如何通过Jenkins声明式Pipeline的parameters块脚本化配置参数？

Absolutely! You can totally replace those GUI-managed variables and radio button selections with a parameters block in your Declarative Pipeline. This approach keeps your pipeline configuration as code—version-controlled, reproducible, and way easier to maintain than manual GUI tweaks.

Here's how you can refactor your existing script to use the parameters block, including support for radio button-style options (via the choice parameter type):

pipeline {
    agent any
    // Define your parameters here - this replaces GUI configs
    parameters {
        // String parameter for task definition family (with a sensible default)
        string(
            name: 'TASK_DEFINITION_FAMILY',
            defaultValue: 'mis-core-dev-notifications-receiver',
            description: 'ECS Task Definition Family name'
        )
        // Radio button-style selection for task definition (predefined options only)
        choice(
            name: 'TASK_DEFINITION',
            choices: ['mis-core-dev-notifications-receiver-a', 'mis-core-dev-notifications-receiver-b', 'mis-core-dev-notifications-receiver-c'],
            description: 'Select the specific Task Definition to use (radio button style)'
        )
        // String parameter for task filter prefix
        string(
            name: 'TASK_FILTER_NAME',
            defaultValue: 'mis-core-dev-notifications-receiver-',
            description: 'Filter prefix for identifying relevant tasks'
        )
        // String parameter for tasks group identifier
        string(
            name: 'TASKS_GROUP',
            defaultValue: 'mis-core-dev...',
            description: 'ECS Tasks Group identifier'
        )
    }

    stages {
        stage('Notifications Receiver (dev)') {
            steps {
                script {
                    // Reference the parameters instead of hardcoding variables
                    def taskDefinitionFamily = params.TASK_DEFINITION_FAMILY
                    def taskDefinition = params.TASK_DEFINITION
                    def taskFilterName = params.TASK_FILTER_NAME
                    def tasksGroup = params.TASKS_GROUP

                    // Your existing logic here - use these variables as needed
                    echo "Using Task Definition: ${taskDefinition}"
                    echo "Task Family: ${taskDefinitionFamily}"
                }
            }
        }
    }
}

Key Details: #

• choice parameter: This creates the exact radio button behavior you want in the Jenkins build trigger UI—users can only pick one predefined option, no free-form input allowed.
• string parameter: Perfect for variables that might need occasional manual adjustments but still have a reliable default. Users can edit the value if needed, or stick with the preset.
• Parameter referencing: Access your parameters using params.PARAMETER_NAME anywhere in your pipeline steps.
• Version control win: All your configuration lives in the Groovy script now, so you can track changes, roll back if something breaks, and share the pipeline config across teams without relying on fragile GUI settings.

When you run this pipeline, Jenkins will prompt you to select/enter values for these parameters before starting the build—just like your old GUI setup, but now it's all codified and manageable.

内容的提问来源于stack exchange，提问作者eekfonky