能否在Jenkins流水线中将参数定义为方法实现复用？并实现参数确认重选

Hey there! Great questions about Jenkins pipeline reusability and parameter validation. Let's break them down one by one:

问题1：能否将参数定义为方法体，以在Jenkins流水线中实现复用？ #

Absolutely! This is actually a super common and recommended practice for Jenkins pipelines. By wrapping your parameter definitions into a reusable method (like your getParameter() example), you eliminate duplicate code, make future updates easier (you only need to modify the method once instead of every instance of the parameters), and keep your pipeline code cleaner.

In declarative pipelines (which you're using here), calling your parameter method directly inside the pipeline block works perfectly—it injects the parameter definitions at pipeline initialization, just like writing the parameters block inline. You can even reuse this method across multiple Jenkinsfiles if you store it in a shared library, making consistency across your pipelines a breeze.

问题2：如何增加参数确认环节，错误则重新选择参数？ #

Your current approach has a small issue: the declarative parameters directive runs only once at pipeline startup. Calling getParameter() inside the catch block later in the pipeline won't re-trigger a parameter input prompt, because that initialization phase is already done.

To fix this and implement the "confirm or re-select" flow, we need to use scripted input steps (which can be triggered dynamically during pipeline execution) instead of declarative parameters. Here's a revised version of your code that works exactly as you want:

// Reusable method to prompt for parameters (uses scripted input for dynamic calls)
def getParameter() {
    return input(
        message: 'Please select your pipeline parameters',
        parameters: [
            string(defaultValue: "API", description: 'What application?', name: 'Application'),
            choice(choices: ['DEV', 'UAT'], description: 'Choose the environment', name: 'Environment')
        ]
    )
}

pipeline {
    agent any
    stages {
        stage("Parameter Validation & Build") {
            steps {
                script {
                    def userSelectedParams = [:]
                    // Loop until user confirms parameters are correct
                    while (true) {
                        // Get new parameters from user
                        userSelectedParams = getParameter()
                        
                        // Display parameters for user to review
                        echo "=== Selected Parameters ==="
                        echo "Application: ${userSelectedParams.Application}"
                        echo "Environment: ${userSelectedParams.Environment}"
                        
                        try {
                            // Prompt user to confirm
                            input message: 'Are these parameters correct?', ok: 'Yes, start build'
                            break // Exit loop if user confirms
                        } catch (err) {
                            // User rejected parameters—loop back to re-prompt
                            echo "⚠️ User rejected parameters, re-prompting for new selections..."
                        }
                    }
                    
                    // Proceed with your build logic using the confirmed parameters
                    echo "🚀 Starting build with validated parameters: ${userSelectedParams}"
                    // sh "./build-script.sh ${userSelectedParams.Application} ${userSelectedParams.Environment}"
                }
            }
        }
    }
}

Key changes explained: #

• The getParameter() method now uses a scripted input step, which triggers a parameter prompt every time it's called (even during pipeline execution, not just at startup).
• We use a while(true) loop to keep re-prompting until the user confirms their selections.
• Confirmed parameters are stored in userSelectedParams, which you can use throughout your build steps.
• If the user clicks "Cancel" during confirmation, the exception is caught, and we loop back to ask for new parameters.

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