Jenkins多分支流水线异常求助：未知「Start of pipeline」报错

Hey there, let's unpack this confusing issue you're running into. That "Start of pipeline" text isn't coming from your declarative script—it's generated by Jenkins core or one of your installed plugins, and the incorrect highlighting as an error is likely a quirk tied to your setup. Here are the most actionable fixes and checks to resolve this:

1. Audit the Pipeline Maven Integration Plugin Version #

Your pipeline relies on the withMaven wrapper, and older versions of this plugin (paired with Jenkins 2.222.3) are known to inject extra log lines like "Start of pipeline" that can get misflagged as errors by Jenkins' UI or log parsing tools.

• Navigate to Manage Jenkins > Plugins > Installed Plugins
• Locate the "Pipeline Maven Integration Plugin" and check its version
• If it’s older than 3.10.x, consider updating it (pro tip: back up Jenkins before updating plugins, especially on older core versions to avoid compatibility hits)

2. Rule Out False Positive Highlighting #

Sometimes Jenkins' UI or third-party log parsing plugins (like Log Parser Plugin) misclassify normal log lines as errors.

• Look closely at the full log context around "Start of pipeline"—is there a real error message above or below this line that’s being overshadowed?
• Disable any custom log parsing rules for this pipeline to see if the highlighting disappears
• Run a stripped-down test pipeline to isolate the issue:

  pipeline { 
      agent any 
      stages { 
          stage ('Test Compile') { 
              steps { 
                  sh 'mvn clean compile' 
              } 
          } 
      } 
  }
  

  If the "Start of pipeline" line doesn’t appear (or isn’t marked as an error) here, the problem is definitely linked to the withMaven wrapper.

3. Dig Into Jenkins Core Logs for Hidden Issues #

Even if the error points to "Start of pipeline", the real root cause might be a hidden initialization failure in the pipeline.

• Go to Manage Jenkins > System Log
• Search for exceptions or warnings that occur around the time your pipeline fails
• Look for entries related to pipeline initialization or Maven integration—these often reveal the actual issue that’s being masked by the misleading log line

4. Workaround: Suppress Unwanted Log Lines #

If updating plugins isn’t feasible right now, you can add a log filter to hide the "Start of pipeline" line from your pipeline logs. Insert this into your pipeline script inside the pipeline block:

options {
    logRotator(numToKeepStr: '5')
    quietPeriod 10
    // Filter out the "Start of pipeline" line
    configure { node ->
        node / logRotator / 'filters' << 'hudson.console.FilterLogFilter' {
            regex('Start of pipeline')
            set('negate', true)
        }
    }
}

This is a temporary workaround to clean up your logs, but it’s still worth addressing the underlying plugin or core compatibility issue long-term.

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