如何在Jenkinsfile中正确配置Active Choices动态Git分支参数？

Let's fix this step by step — your issue comes from a few small mistakes in the parameter class selection, Groovy script syntax, and missing error handling for the git command. Here's how to get your dynamic branch/tag selector working:

1. Use the Correct Active Choices Parameter Class #

You're using ChoiceParameter, which is Jenkins' native static choice parameter. For dynamic, script-generated options, you need to use ActiveChoiceParameter (for non-reactive selections) or ActiveChoiceReactiveParameter (if you need the options to update based on other parameters). Since you don't mention dependencies on other parameters, ActiveChoiceParameter is the right fit.

2. Fix the Groovy Script & Add Error Handling #

Your original script had a syntax error (it.split([1] instead of it.split()[1]) and lacked checks for git command failures. Adding error handling will help you debug why the fallback "error" is showing up.

Working Jenkinsfile Examples #

Option 1: Inline Groovy Script

properties([
    parameters([
        [$class: 'ActiveChoiceParameter',
         choiceType: 'PT_SINGLE_SELECT',
         description: 'Select code branch or tag name',
         name: 'code_release_branch',
         script: [$class: 'GroovyScript',
                  fallbackScript: [
                      classpath: [],
                      sandbox: false,
                      script: 'return ["ERROR: Failed to fetch branches/tags"]'
                  ],
                  script: [
                      classpath: [],
                      sandbox: false,
                      script: '''
                          // Execute git command to fetch refs
                          def gitCmd = "git ls-remote -t -h ssh://git@abc.com/code/code.git".execute()
                          gitCmd.waitFor() // Wait for command completion
                          
                          // Check if git command succeeded
                          if (gitCmd.exitValue() != 0) {
                              def errorDetails = gitCmd.err.text.trim()
                              return ["ERROR: ${errorDetails ?: 'Git command failed unexpectedly'}"]
                          }
                          
                          // Process output to extract branches/tags
                          return gitCmd.text.readLines().collect { line ->
                              def refPath = line.split()[1]
                              refPath.replaceAll('refs/heads/', '')
                                     .replaceAll('refs/tags/', '')
                                     .replaceAll("\\^\\{\\}", '')
                          }.unique().sort() // Remove duplicates and sort options
                      '''
                  ]
                 ]
        ]
    ])
])

Option 2: Using Jenkins Managed File

First, ensure your managed file (ID: 6cd2a674-c02d-44b0-87cb-b32f1fcdc0c3) contains this corrected script:

def gitCmd = "git ls-remote -t -h ssh://git@abc.com/code/code.git".execute()
gitCmd.waitFor()

if (gitCmd.exitValue() != 0) {
    def errorDetails = gitCmd.err.text.trim()
    return ["ERROR: ${errorDetails ?: 'Git command failed'}"]
}

return gitCmd.text.readLines().collect { line ->
    def refPath = line.split()[1]
    refPath.replaceAll('refs/heads/', '')
           .replaceAll('refs/tags/', '')
           .replaceAll("\\^\\{\\}", '')
}.unique().sort()

Then update your Jenkinsfile to reference the managed file correctly:

properties([
    parameters([
        [$class: 'ActiveChoiceParameter',
         choiceType: 'PT_SINGLE_SELECT',
         description: 'Select code branch name',
         name: 'code_release_branch',
         script: [$class: 'GroovyScript',
                  fallbackScript: [
                      classpath: [],
                      sandbox: false,
                      script: 'return ["ERROR: Failed to fetch branches/tags"]'
                  ],
                  script: [
                      classpath: [],
                      sandbox: false,
                      script: '6cd2a674-c02d-44b0-87cb-b32f1fcdc0c3' // Your managed file ID
                  ]
                 ]
        ]
    ])
])

Key Notes to Avoid Future Issues #

• Git Authentication: For SSH URLs, make sure the Jenkins service user (e.g., jenkins) has a valid SSH key in its ~/.ssh directory, and the target Git server is added to known_hosts. For HTTPS, you can embed credentials in the URL (not recommended for public repos) or use Jenkins credential bindings (requires adjusting the script to pull credentials from Jenkins).
• Script Security: If your Jenkins instance enforces script security, you may need to approve the Groovy methods used (execute(), waitFor(), etc.) via Manage Jenkins > In-process Script Approval.
• Sandbox Mode: Disabling sandbox is okay for trusted scripts, but if you need sandbox enabled, you'll have to ensure all required methods are approved.

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