Common Jenkins Pipeline Debugging Issues and Solutions

The article presents a collection of Jenkins pipeline debugging scenarios encountered by various users, each followed by practical answers and code examples.

Issue 1: Using Python's gitlab library to fetch branch information is heavy; the recommended approach is to use the httpRequest plugin for lightweight HTTP calls.

Issue 2: Retrieving plain-text credentials fails; the solution is to use a withCredentials {} block, ensuring the credential ID is specified and using double quotes for variable interpolation.

Issue 3: For scanning a Vue project with Sonar, the official sonar-scanner (or its Jenkins integrations) must be used.

Issue 4: Git Parameter plugin may return the wrong branch; configure the advanced settings to point to the correct repository or rely on trigger-based branch passing.

Issue 5: Converting a string to JSON in a Harbor API call can be done with the readJSON step from the "Pipeline Utility Steps" plugin, or via a native Groovy method:

import groovy.json.*
@NonCPS
def GetJson(text){
    def prettyJson = JsonOutput.prettyPrint(text)
    new JsonSlurperClassic().parseText(prettyJson)
}

Issue 6: To obtain response body text from the httpRequest plugin, use response.content while response.status gives the status code.

Issue 7: Restarting a specific stage in a declarative pipeline can be achieved by sending a POST request to the Jenkins API with the stage name.

Issue 8: The choice step's abort message cannot be customized; no parameter exists for this.

Issue 9: To force‑kill a stuck build without restarting Jenkins, append kill to the build URL and press Enter.

Issue 10: Splitting a Git repository URL to extract the project name can be done with Groovy's split method:

repoUrl = "http://gitlab.com/demo/demo-test-service.git"
projectName = repoUrl.split("/")[-1] - ".git"

The article concludes with a promotional note about a DevOps pipeline tutorial and encourages readers to join the community for further learning.